Hi,
Is there any change since 1st of December?

Thanks

---

“The good thing about science is that it's true whether or not you believe in it.” ― Neil deGrasse Tyson

What comes on my mind are several things you could try if possible.
First try to "Reset project", run "Benchmark" and observe the behavior. And if this does not help the next thing you can try is:
Second rename the host. If the server has downvoted this particular host (which could be because of a lot of reasons, as the algorithm is pretty complex) this will let it find your renamed host as a totally new machine. This way it will start from the beginning the whole "touching" process. Probably you will see at first glance some strange estimation times which is normal. The point is that the server now should try the 'avx' app on the new host. In this meaning could you post the row from the 'stdoutea.txt' where the 'Processor features:' is?
And finally, if nothing helps you still could use the Anonymous platform by adding 'app_info.xml' file to the project's folder with the appropriate data.
Resetting the server is not an option at all. There is a lot of checksums, that are tightly coupled with almost every specific record including the host performance against specific app.
I still will discuss this issue with Kyong though.

Georgi

---

“The good thing about science is that it's true whether or not you believe in it.” ― Neil deGrasse Tyson

I forgot to mention one thing, which you probably are aware already but still - if renaming the host do the trick, you can merge your hosts later on (the old name and the new one) as they are still the same machine.

---

“The good thing about science is that it's true whether or not you believe in it.” ― Neil deGrasse Tyson

I'm glad that it worked out!

And yes, there are new builds for some of the applications.

Happy holidays!

---

“The good thing about science is that it's true whether or not you believe in it.” ― Neil deGrasse Tyson

...use the Anonymous platform by adding 'app_info.xml' file to the project's folder with the appropriate data.

I've been trying to use an app_info.xml file to only get the more energy efficient sse instruction set. The problem is that since both CPU and GPU WUs are named "period_search" it causes problems. If I only include parameters to limit CPU WUs to sse3_linux that works fine and I only get sse3_linux CPU WUs but I don't get any GPU WUs. When I try to include a section for the GPU WUs, which I shouldn't even need if the WUs had been named "period_search_CPU" and "period_search_GPU", I do not get any GPU WUs. I've tried restarting BOINC and rebooting the computer but I get the same message each time: "Not requesting tasks: don't need (CPU: ; NVIDIA GPU: )"
Here's the latest version of the app_info.xml I've tried:

<app_info>
<app>
    <name>period_search</name>
</app>
<file_info>
    <name>period_search_10213_x86_64-pc-linux-gnu__sse3_linux</name>
    <executable/>
</file_info>
<app_version>
    <app_name>period_search</app_name>
    <version_num>10213</version_num>
    <avg_ncpus>1.000000</avg_ncpus>
    <flops>216957983664.719849</flops>
    <plan_class>sse3_linux</plan_class>
    <api_version>7.17.0</api_version>
    <file_ref>
        <file_name>period_search_10213_x86_64-pc-linux-gnu__sse3_linux</file_name>
        <main_program/>
    </file_ref>
</app_version>
<file_info>
    <name>period_search_10217_x86_64-pc-linux-gnu__cuda118_linux</name>
    <executable/>
</file_info>
<app_version>
    <app_name>period_search</app_name>
    <version_num>10217</version_num>
    <platform>x86_64-pc-linux-gnu</platform>
    <avg_ncpus>0.010000</avg_ncpus>
    <flops>2846331819585.037598</flops>
    <plan_class>cuda118_linux</plan_class>
    <api_version>7.17.0</api_version>
    <file_ref>
        <file_name>period_search_10217_x86_64-pc-linux-gnu__cuda118_linux</file_name>
        <main_program/>
    </file_ref>
</app_version>
</app_info>

I put a copy of both executables in the folder before restarting. If anyone can tell me how to make both CPU and GPU work I'd appreciate it.
I suspect that as soon as the executable version is upgraded the app_info.xml file will stop working and no WUs will be DLed.
The best solution would be to give us the ability select which CPU instruction set we want in our Project Preference file. Better still would be to only compile the most energy efficient sse instruction set.
Also, another quirk of naming both period_search is that the commands

<project_max_concurrent>36</project_max_concurrent>

and

<project_max_concurrent>36</project_max_concurrent>

count the total number of WUs = CPU WUs + GPU WUs. Making the behavior different than any other BOINC project.

---

You are using the incorrect task limitation in your app_info or app_config.
Project_max_concurrent applies to all tasks, both cpu and gpu in a project.

If you want to limit the number of tasks being crunched for each device type, use the max_concurrent statement in each app_version section. Read the configuration options documentation.

https://boinc.berkeley.edu/wiki/Client_configuration#Application_configuration

---

A proud member of the OFA (Old Farts Association)

You are using the incorrect task limitation in your app_info or app_config.
Project_max_concurrent applies to all tasks, both cpu and gpu in a project.

If you want to limit the number of tasks being crunched for each device type, use the max_concurrent statement in each app_version section. Read the configuration options documentation.

https://boinc.berkeley.edu/wiki/Client_configuration#Application_configuration

If you actually read that link you'd see it goes inside <app></app> and not <app_version>.
Are you trying to say that's why I can only get CPU WUs and never GPU WUs when I use an app_info?
BTW, this happens even if I have no app_config file and <max_concurrent> does not even appear in my app_info file.

---