Hello everyone,

We will be running server maintenance on June 1st, 2023 at 11:30 AM EDT.
Maintenance should be done by the end of the day.
An announcement will be made on this thread when maintenance is over.

Thanks,
Kevin

Thanks Kevin. Appreciate the notice.

I'll be sure to prefetch enough work. Thank you

---

Hello everyone,

We will be running server maintenance on June 1st, 2023 at 11:30 AM EDT.
...
Thanks,
Kevin

Hi Kevin, as I have already pointed out to Tom some time ago, it would be nice (atually great) if the time unit
is also noted/shown in UTC form.

Just an idea ....

cheers S-F-V

https://dateful.com/time-zone-converter

---

Hi Kevin, as I have already pointed out to Tom some time ago, it would be nice (atually great) if the time unit
is also noted/shown in UTC form.

Just an idea ....

cheers S-F-V

I will keep this in mind next time I make an announcement.
Thank you for the feedback.

Server maintenance is completed!

Data exchange is still not available..

Data exchange is still not available..

We have received workunits within the last few minutes and our upload and download server appears to be operating like expected. Are you still have issues with data exchange?
.

Now that power maintenance is complete, could you do us people with Intel K processors a favor? Please make Modfit a separate category so we can exclude multicore tasks. I have to abort-by-user all 8-core tasks because they hang my systems.
FYI, the K processor has four real and four virtual cores. That works if, and only if, both the virtual core and the real core that manages it try to access the same instruction (e.g.: double-precision floating point) at the same time. When this happens, both the virtual and the real core go into a wait state forever. I have to manually suspend the task and renew it to release the wait states. This happens more than once before each 8-core task completes. If I abort the 8-core tasks by-user without selecting "no more tasks" first, the tasks I just aborted come back to me as new tasks. Getting BOINC, Microsoft, and/or Intel to fix this is useless.

---

Please make Modfit a separate category so we can exclude multicore tasks.

It is a separate category, just disable "Milkyway@home N-Body Simulation" in your project preferences and you won't get any multicore tasks anymore. Other possibility is to make them single core with this app_config.xml file in your milkyway project dir:

<app_config>
 <app_version>
  <app_name>milkyway_nbody</app_name>
  <plan_class>mt</plan_class>
  <avg_ncpus>1</avg_ncpus>
  <cmdline>--nthreads 1</cmdline>
 </app_version>
</app_config>

the K processor has four real and four virtual cores

That's called hyperthreading and nearly every current processor has it. "K" means unlocked multiplier and has nothing to do with it.

Is it possible, that you don't let BOINC use 100% of CPU time? As that's most common reason for stuck nBody WUs and not hypethreading.

---