app_config.xml question

[siu77]

Greetings!

Code: Alles auswählen

<app_config>

  <app>
    <name>ECM P2 (up to 20 GB RAM)</name>
    <max_concurrent>1</max_concurrent>
  </app>

</app_config>

I want to run only one 20 GB task. How this can be achieved? What is the exact name of this task type?

p.s. Of course, there is a way to exclude all except 20 GB tasks in yoyo@home preferences, and run <project_max_concurrent> globally. Like this:

Code: Alles auswählen

<app_config>

<project_max_concurrent>1</project_max_concurrent>

</app_config>

It works, but other tasks are not calculating simultaneously.

Thank you.

[gemini8]

I don't know the application's name, but you can just put anything into the file as placeholder, which will make BOINC tell you the names it already knows.
So, if you have run one of these tasks, BOINC will tell you its name, and you can then put it into the app_config.xml file.

[siu77]

So, if you have run one of these tasks,

A, that's the thing. I've tried this before, but it told me only one type 'sieve'. Thank you very much.

In case anyone is interested, the exact name is 'ecmP2-20G'.

[gemini8]

My pleasure.

[Michael H.W. Weber]

In case anyone is interested, the exact name is 'ecmP2-20G'.

...thank you - I was also looking for this.
So far, I only run the "ecmP2" 10 GB RAM tasks, now I can add the 20 GB variants as well...

Michael.

[siu77]

Unfortunately, this doesn't work. That is, if a certain number of tasks are already loaded, the max_concurrent limit applies, and only one 20 GB unit is actually counted. However, with this app_config.xml, new sieve and ecm units aren't loaded for some reason.

If app_config.xml is empty, log is:

Code: Alles auswählen

yoyo@home | Requesting new tasks for CPU and AMD/ATI GPU and Intel GPU
yoyo@home | Scheduler request completed: got 1 new tasks

if app_config.xml looks like this:

Code: Alles auswählen

<app_config>

  <app>
    <name>ecmP2-20G</name>
    <max_concurrent>1</max_concurrent>
  </app>

</app_config>

then the server's response is:

Code: Alles auswählen

yoyo@home | Requesting new tasks for AMD/ATI GPU and Intel GPU
yoyo@home | Scheduler request completed: got 0 new tasks

It somehow forgets about CPU.

[siu77]

now I can add the 20 GB variants as well...

Michael.

Your welcome. But, please, double check your downloads with new app_config enabled, 'cause mine are just not working as they should.

[gemini8]

Unfortunately, this doesn't work. That is, if a certain number of tasks are already loaded, the max_concurrent limit applies, and only one 20 GB unit is actually counted. However, with this app_config.xml, new sieve and ecm units aren't loaded for some reason.

If app_config.xml is empty, log is:

Code: Alles auswählen

yoyo@home | Requesting new tasks for CPU and AMD/ATI GPU and Intel GPU
yoyo@home | Scheduler request completed: got 1 new tasks

if app_config.xml looks like this:

Code: Alles auswählen

<app_config>

  <app>
    <name>ecmP2-20G</name>
    <max_concurrent>1</max_concurrent>
  </app>

</app_config>

then the server's response is:

Code: Alles auswählen

yoyo@home | Requesting new tasks for AMD/ATI GPU and Intel GPU
yoyo@home | Scheduler request completed: got 0 new tasks

It somehow forgets about CPU.

Unless something's changed in the BOINC code, BOINC should ask for more CPU work as well, provided your CPU doesn't run anything else.
I heard suggestions about planned changes that could affect the workings of app_config.xml, and if these have already come, you might want to specify the other sub-projects as well to try if that helps. Don't know any specifics, unfortunately.

On the other hand, the server might just have been empty regarding the P2-20 tasks.

[Michael H.W. Weber]

1) Yoyo@home does not provide GPU apps, yet. But it reports to have looked for these. It does not imply that it is ONLY looking for GPU tasks. In fact, I use the same app_config.xml in the regular "ecmP2" (i.e. 10 GB WUs) context and it does download the EcmP2 tasks up to the limit I defined in that file.
2) Yes, the EcmP2 are limited and often the server does not provide enough work for me to process. I BELIEVE this could very well be true for the novel 20 GB WUs, too.
3) What I am unsure about is whether the max_concurrent setting WITHIN the <app> part of the configuration file REALLY restricts to that app (as it should). I note this, because I don't get work for OTHER subtype tasks from Yoyo@home when 5 EcmP2 WUs are running (that is my currently set maximum of simultaneously processed 10 GB EcmP2 WUs). Not sure why this is the case and I really did not look exactly into it as that machine is remotely controlled and I have limited access to it...

Michael.

[siu77]

After consulting with the AI, I ended up with this app_config.xml:

Code: Alles auswählen

<app_config>

<project_max_concurrent>8</project_max_concurrent>

<app>
<name>ecmP2-20G</name>

<max_concurrent>1</max_concurrent>
<!-- Prevents BOINC from downloading new ecmP2-20G tasks if one is already running or waiting -->
<donotrequesttasks/>

</app>
</app_config>

project_max_concurrent = max CPU threads

And after I increased the task inventory limit to 5 days, downloading other tasks started. But only 8 at a time are present.

I think the problem is caused by the following. The preliminary estimated calculation time shown by boinc for ECM tasks is over 3 days, and for 20GB ECM tasks, over 14 days. The boinc algorithm, "afraid" of exceeding the limit, doesn't download any unnecessary data. At the same time, access to this website is restricted from Russia, so the data adjusting these large numbers doesn't reach the project server.

In any case, it appears the issue has been resolved. Thanks everyone.