LHC@home

There are 4 unsent WUs for Atlas:

22/01/2017 22:22:37 | LHC@home | Sending scheduler request: To fetch work.
22/01/2017 22:22:37 | LHC@home | Requesting new tasks for CPU
22/01/2017 22:22:39 | LHC@home | Scheduler request completed: got 0 new tasks
22/01/2017 22:22:39 | LHC@home | No tasks sent
22/01/2017 22:22:39 | LHC@home | No tasks are available for ATLAS Simulation

---

Supporting BOINC, a great concept !

Now there are more than 100 Atlas-tasks, but still I get:

23/01/2017 15:11:50 | LHC@home | Sending scheduler request: To fetch work.
23/01/2017 15:11:50 | LHC@home | Requesting new tasks for CPU
23/01/2017 15:11:52 | LHC@home | Scheduler request completed: got 0 new tasks
23/01/2017 15:11:52 | LHC@home | No tasks sent
23/01/2017 15:11:52 | LHC@home | No tasks are available for ATLAS Simulation

---

Supporting BOINC, a great concept !

Same for me, and I saw others complaining about getting WU: https://lhcathome.cern.ch/lhcathome/forum_thread.php?id=4101

I've asked the admins to take a look.

Got 4 Atlas-WUs

They seem to be 1-Core

So far I didn't set up an app_config, I wanted to see what happens without.

My LHC-Project-Settings:

Max # Jobs: No Limt
Max # CPUs: 4

---

Supporting BOINC, a great concept !

Will the Atlas-WUs here take into account the settings regarding NumberOfWUs and NumberOfCores from the Website or do we have to setup an app_config ?

They should do as they act upon the scheduling in the server rather than the client. I am just testing now for myself but there are no tasks.

Edit: It doesn't work at the moment but we should be able to get it working.

Could you make some progress on this ?

Is "MAX # CPUs" the number for the cores in an WU, so when I set this to 4, I get 4-Core-WUs for Atlas ?

---

Supporting BOINC, a great concept !

Due to the large number of sixtrack tasks in the queue it's very hard to get an ATLAS (or any other app) task at the moment.

In my config I have

Max # jobs No limit
Max # CPUs 2

and 4-cores on my PC.

When I get ATLAS WU I get 2 at a time which makes sense, but they run single-core only.

Has anyone tried app_config.xml?

David wrote:

Has anyone tried app_config.xml?

I'm just working on it, but wanted to let the 4x 1-Core-WUs first finish or should I abort them?

---

Supporting BOINC, a great concept !

Has anyone tried app_config.xml?

Finally got an ATLAS-task. I already had the app_config prepared to run a 4 core VM.

It just started 5 minutes ago. When it's 1 job using 4 cores, it will run for about 2.5 hours, I think.

The single core I had before used 9 hours and 40 minutes (elapsed)

David wrote:

Has anyone tried app_config.xml?

I'm just working on it, but wanted to let the 4x 1-Core-WUs first finish or should I abort them?

Just downloaded a new WU with app_config, it is a 4-Core-WU!

For safety reasons I had changed the Web-Config "Max # CPU" and "Max # Jobs" to <No limit>

---

Supporting BOINC, a great concept !

I just got one with the setting no limit, I now have one atlas using 24cores.

That's not what I expected!

Setting my cores preference to 2 did what I expected.

did this ever get fixed?

http://atlasathome.cern.ch/forum_thread.php?id=534&postid=4977#4977

It just started 5 minutes ago. When it's 1 job using 4 cores, it will run for about 2.5 hours, I think.

The 4-core VM (configured with app_config) has finished as expected =>> https://lhcathome.cern.ch/lhcathome/result.php?resultid=115673716

I just got one with the setting no limit, I now have one atlas using 24cores.

That's not what I expected!

I'd be interested to know if that WU works and its performance (bad I expect)! We need to limit to max 8 cores.

did this ever get fixed?

http://atlasathome.cern.ch/forum_thread.php?id=534&postid=4977#4977

No, but I think the project preferences settings that Laurence introduced should avoid the problem because the server knows when it sends the WU the number of cores and how much memory it will use.

I've got some 28 Core WU's, after 90 sec they are only using 50% of one core - 3,8% of total CPU,

So limiting to 8 core might be a good idea.

I quit it but I can change it back to try again and let you know. It will be on my 14core/28thread computer so it's contained within one CPU.

Nils Høimyr wrote:

We have restarted our daemons with the --allapps flag for the feeder now.

Please let us know if you get CMS and Theory tasks quicker now.

27/01/2017 11:30:13 | LHC@home | Sending scheduler request: To fetch work.
27/01/2017 11:30:13 | LHC@home | Requesting new tasks for CPU
27/01/2017 11:30:14 | LHC@home | Scheduler request completed: got 0 new tasks
27/01/2017 11:30:14 | LHC@home | No tasks sent
27/01/2017 11:30:14 | LHC@home | No tasks are available for ATLAS Simulation

Atlas shows 10 WUs to send on ServerStatusPage, so is Atlas out of WUs or does the scheduler still have a problem ?

---

Supporting BOINC, a great concept !

I've had no ATLAS tasks for 2 days now, but the LHC@Home guys are working on a solution to the scheduling problem.

I have put a few more WU in the queue in case people get lucky enough to have an ATLAS task scheduled.

I tried to do 2 24core tasks but they both seemed to turn into the never ending tasks.

I quit one after 9hrs and the other after 22hrs.

I can try again if there is some help to debug why they hung?

I'd be interested to know if that WU works and its performance (bad I expect)! We need to limit to max 8 cores.

+1 David

i have crunched 4 4core multicore atlas tasks today. they all had pretty much the same running time and cpu time.
for three of them i got about 64 credits, but for the last one i got about 450.
so i wondered why i get nearly 7 times more points for pretty much the same computation time.
does anyone else have seen this behaviour? have you changed something or is this a bug?

here are the wus im talking about:
https://lhcathome.cern.ch/lhcathome/result.php?resultid=117806105
https://lhcathome.cern.ch/lhcathome/result.php?resultid=117805627
https://lhcathome.cern.ch/lhcathome/result.php?resultid=117801849
https://lhcathome.cern.ch/lhcathome/result.php?resultid=117678817

Just cross your fingers that creditnew (screw) keeps the larger credit value for
your ATLAS tasks.

It usually takes 11 validated tasks for creditnew to determine a baseline for your system, Since you switched from sixtrack to ATLAS with a bunch of invalidated sixtrack tasks it will be interesting to see what creditnew does.

from this point forward.