Posts by ahorek's team

1) (Message 8397)
Posted 6 hours ago by ahorek's team
Post:
note that just a high temperature isn't a problem. Modern CPUs like yours are designed to keep the maximum temperature limit around 80-95°C under load. This is normal and it also shouldn't cause shutdowns or any issues.

if your PC with 8/16 cores can't sustain 3 tasks load, there's something wrong and you should really check your cooling solution. It's not a problem with the app.

you can configure the app to use a less optimized version by putting app_config.xml into your project's folder and then restart the client
<app_config>
  <app_version>
    <app_name>period_search</app_name>
    <plan_class></plan_class>
    <cmdline>--optimization 3</cmdline>
  </app_version>
</app_config>

this way the app won't hit the CPU that hard, but it'll also be slower = less effective. It's just a workaround and reducing the maximum TDP as I suggested before is usually a better choice.
2) (Message 8393)
Posted 1 day ago by ahorek's team
Post:
recent CPUs like your Zen 3 boost up higher and higher until they bump into the power, thermal, or frequency limits. Reaching 80C or 175F under heavy load is normal and by design.
unlike other apps like Einstein, Asteroids app heavily uses optimized CPU features like FMA and better CPU utilization means more heat.

I would play with the Bios / Ryzen Master... lowering power limits / disabling PBO could help significantly with temps without sacrificing too much performance.
Another factor is your integrated GPU. GPU apps are not very effective on this project and you'll likely slow down all your CPU tasks due to shared thermal limits...
3) (Message 8392)
Posted 1 day ago by ahorek's team
Post:
hopefully, there'll be a new release soon fixing the issue. For now, you can disable AVX, see https://asteroidsathome.net/boinc/forum_thread.php?id=1024&postid=8372#8372
4) (Message 8386)
Posted 7 days ago by ahorek's team
Post:
The ETA is inaccurate because BOINC hasn't benchmarked the new app yet. It'll settle after finishing a few WUs. Anyway, I see nairb's tasks were successful, which is a good sign. Thank you both!
5) (Message 8383)
Posted 7 days ago by ahorek's team
Post:
> Is this bug known?

no, it's not. "Signal 35" indicates the app has been killed by the OS for some reason. Perhaps, out of memory killer?
6) (Message 8380)
Posted 8 days ago by ahorek's team
Post:
the new version has all optimizations in a single application and chooses between them dynamically based on your hardware capabilities.

you can check which optimizations were used in the stderr log
BOINC client version 8.0.1
Application: ../../projects/asteroidsathome.net_boinc/period_search_10220_x86_64-pc-linux-gnu
Version: 102.20.1.1
CPU: AMD Ryzen 9 7950X 16-Core Processor            
RAM: 15.35 GB
Using AVX512 SIMD optimizations.
7) (Message 8379)
Posted 8 days ago by ahorek's team
Post:
thanks, it turns out I made a mistake while building the app. Here's an updated version https://fileport.io/qCXSSnT4xCJQ

could you please check?
8) (Message 8374)
Posted 8 days ago by ahorek's team
Post:
Thanks for your patience. Hopefully, we will be able to release a patched version this week.
9) (Message 8372)
Posted 8 days ago by ahorek's team
Post:
hmmm, it should work. Alternatively, you can force SSE3 optimizations with app_config.xml

<app_config>
  <app_version>
    <app_name>period_search</app_name>
    <plan_class></plan_class>
    <cmdline>--optimization 3</cmdline>
  </app_version>
</app_config>

however, expect a slightly worse performance compared to the AVX version.
10) (Message 8370)
Posted 8 days ago by ahorek's team
Post:
you can test it with the sample work unit "period_search_in".

For https://boinc.berkeley.edu/wiki/Anonymous_platform put the binary in the project's folder, create app_info.xml, and restart the boinc client.

/var/lib/boinc/projects/asteroidsathome.net_boinc/app_info.xml
<app_info>
 <app>
    <name>period_search</name>
 </app>
 <file_info>
  <name>period_search_BOINC_linux_10220_x64_universal_linux_Release</name>
  <executable/>
 </file_info>

<app_version>
    <app_name>period_search</app_name>
    <version_num>10220</version_num>
    <avg_ncpus>1.000000</avg_ncpus>
    <plan_class>avx_linux</plan_class>
    <file_ref>
        <file_name>period_search_BOINC_linux_10220_x64_universal_linux_Release</file_name>
        <main_program/>
    </file_ref>
</app_version>
</app_info>
11) (Message 8368)
Posted 9 days ago by ahorek's team
Post:
it's indeed a bug in the AVX implementation, that mostly affects hosts with legacy Intel CPUs like Sandy Bridge on Linux.

we already have a fix, but releasing it would take some time (about a week)

could you test this version? it would be helpful if you could double-check it works as expected on these systems. You can also run regular tasks using the anonymous platform with it.
https://fileport.io/wWq7w3weQMBq

thanks and sorry for the inconvenience!
12) (Message 8363)
Posted 10 days ago by ahorek's team
Post:
the new arm64 native application now utilizes asimd instruction set, so it should be more close and likely faster than the emulated x86_64 version.
13) (Message 8362)
Posted 10 days ago by ahorek's team
Post:
version 102.20 has been released. It includes new hand-written optimizations for asimd instruction set, that should give a substantial performance boost on supported 64-bit ARM v8 processors like Apple Mx and RPis.
14) (Message 8361)
Posted 10 days ago by ahorek's team
Post:
the new app is finally out. Give it a try!
15) (Message 8353)
Posted 28 days ago by ahorek's team
Post:
we have decided to detect available features by the app instead of having multiple apps and relying on what the boinc client reports. Once (hopefully soon) we release a new version, this boinc feature won't be relevant to us anymore.

btw Primegrid has used the same technique for a long time. http://www.primegrid.com/forum_thread.php?id=10534

until then, there's still an option to run optimized versions on Windows via anonymous platform (if your hardware supports it). Compared to FMA it's up to 20% faster on Intel and slightly faster on AMD (Zen 4). There are rumors that Zen 5 will improve the AVX512 performance, which might be interesting.
16) (Message 8331)
Posted 27 Mar 2024 by ahorek's team
Post:
I've tested the alpha 8.0 version and have no issues getting new tasks. Could you double-check if CPU work is enabled in your account manager preferences?
Also, the client may not request new work, if your host is busy running other projects.
17) (Message 8323)
Posted 27 Mar 2024 by ahorek's team
Post:
you can download avx512 apps from
https://asteroidsathome.net/boinc/download/period_search_10215_windows_x86_64__avx512_win10.exe
https://asteroidsathome.net/boinc/download/period_search_10215_x86_64-pc-linux-gnu__avx512_linux

ensure your CPU has avx512 support (like AMD Zen 4, Intel Ice Lake, Intel Sapphire Rapids etc.).
18) (Message 8316)
Posted 25 Mar 2024 by ahorek's team
Post:
is there anything in the event log?
19) (Message 8312)
Posted 19 Mar 2024 by ahorek's team
Post:
Keith's issue was unrelated to the android's app.

The new android app still hasn't been released, so the "Number of lc points is greater than POINTS_MAX = 1000" problem is still present. The code is ready, we just need to build it and upload a new release to the server. Unfortunately, I don't have access to the server, so it has to wait for Georgi & Radim once they have time to do it.
20) (Message 8308)
Posted 18 Mar 2024 by ahorek's team
Post:
Cause I always get SSE3 app and never get AVX/FMA ones. I think my CPU 5700X support these.

you're right, the fact that BOINC is stuck with SSE3 and never tries new, more optimized apps (on some hosts) is a bug either with the server configuration or the BOINC server code.
however, there are more related issues with this approach. BOINC doesn't reliably report all necessary features on all platforms. Windows is the most important one, but the same issue is on BSD and Macs all of them have their specific way of detecting features, so we have decided to develop a new app that selects the best implementation at runtime instead of relying on what the BOINC client says. It's already in the testing phase.

if you have this issue and don't want to wait for the next release, using an anonymous platform as Keith suggested is a workaround to get the best performance. I admit it's inconvenient for users who aren't familiar with it, but please be patient, we're working on a solution :)


Next 20