Message boards :
ATLAS application :
Very long tasks in the queue
Message board moderation
Previous · 1 . . . 3 · 4 · 5 · 6
Author | Message |
---|---|
![]() ![]() Send message Joined: 2 Sep 04 Posts: 450 Credit: 171,552,275 RAC: 64,126 ![]() ![]() ![]() |
|
![]() ![]() Send message Joined: 18 Dec 16 Posts: 123 Credit: 37,495,365 RAC: 0 ![]() ![]() |
Sorry, it is already uploaded ... I guess this one, taskID=10959636: https://lhcathome.cern.ch/lhcathome/result.php?resultid=132850817 We are the product of random evolution. |
![]() ![]() Send message Joined: 2 Sep 04 Posts: 450 Credit: 171,552,275 RAC: 64,126 ![]() ![]() ![]() |
Sorry, it is already uploaded ... Nope, I think it was this one: https://lhcathome.cern.ch/lhcathome/result.php?resultid=132801696 And yes, it has taskID=10959636 ![]() Supporting BOINC, a great concept ! |
Send message Joined: 18 Dec 15 Posts: 1571 Credit: 67,087,526 RAC: 169,702 ![]() ![]() ![]() |
I now also have a longrunner with taskID=10959636 - event no. 169 after 17:20 hours. David, will these longrunners one day be in a separate selection category in the personal settings? |
Send message Joined: 2 May 07 Posts: 1752 Credit: 136,505,063 RAC: 28,175 ![]() ![]() ![]() |
fyi this is a longrunner with problems: https://lhcathome.cern.ch/lhcathome/workunit.php?wuid=64572687 |
Send message Joined: 18 Dec 15 Posts: 1571 Credit: 67,087,526 RAC: 169,702 ![]() ![]() ![]() |
Since several days ago, the situation with these long tasks is the following (at least this is my experience): I have noticed that all "Long runners" (which, when being downloaded, show a remaining time of a fews days) error out shortly after start. The other tasks (showing a remaining time of a few hours) are all going well. So what I am doing now is: once such a "Long runner" is downloaded, I abort it immediately. Remains to hope that these "Long Runners" will soon be able to be selected as a seperate sub-project, so that people can choose not to download these. |
![]() ![]() Send message Joined: 18 Dec 16 Posts: 123 Credit: 37,495,365 RAC: 0 ![]() ![]() |
Maybe a new beta application for long-runners could be started, for example after completing the merger with ATLAS@Home, so that testing those would be on a voluntary basis. We are the product of random evolution. |
Send message Joined: 18 Dec 15 Posts: 1571 Credit: 67,087,526 RAC: 169,702 ![]() ![]() ![]() |
Maybe a new beta application for long-runners could be started, for example after completing the merger with ATLAS@Home, so that testing those would be on a voluntary basis. I strongly endorse this proposal |
Send message Joined: 9 Dec 14 Posts: 202 Credit: 2,533,875 RAC: 0 ![]() ![]() |
Maybe a new beta application for long-runners could be started, for example after completing the merger with ATLAS@Home, so that testing those would be on a voluntary basis. https://lhcathome.cern.ch/lhcathome/forum_thread.php?id=4157&postid=29301#29301 |
Send message Joined: 2 May 07 Posts: 1752 Credit: 136,505,063 RAC: 28,175 ![]() ![]() ![]() |
The Download-File for the new tasks is 425 MByte? |
Send message Joined: 2 May 07 Posts: 1752 Credit: 136,505,063 RAC: 28,175 ![]() ![]() ![]() |
The current ATLAS tasks process 100 events, but as an experiment we have sent some tasks with 1000 events. We would like to see if it's possible to run tasks like these on ATLAS@Home because this is the same number of events each task processes on the ATLAS grid. It would make things a lot easier if the same tasks could run on ATLAS@Home as on the rest of the ATLAS grid. This is the beginning of this thread from David! What's about 1.000 events running in nativeApp for Linux only? There is not so a overhead and is running very stable. In the preferences is a flag useful therefore. Is there a second chance...... |
![]() Send message Joined: 17 Sep 04 Posts: 93 Credit: 28,760,845 RAC: 14,092 ![]() ![]() ![]() |
The current ATLAS tasks process 100 events, but as an experiment we have sent some tasks with 1000 events. We would like to see if it's possible to run tasks like these on ATLAS@Home because this is the same number of events each task processes on the ATLAS grid. It would make things a lot easier if the same tasks could run on ATLAS@Home as on the rest of the ATLAS grid. And I wish there were a way for ATLAS to identify the Windows machines that could process these successfully, and have an opt-in option for the user. I had no problems with these when they were available. Thanks! Regards, Bob P. |
Send message Joined: 15 Nov 14 Posts: 602 Credit: 24,371,321 RAC: 0 ![]() ![]() |
What's about 1.000 events running in nativeApp for Linux only? Yes, that would be a good use for native ATLAS. I devote a Haswell machine that runs 24/7 (without VitualBox) to it, and it could use some long ones. |
Send message Joined: 18 Dec 15 Posts: 1571 Credit: 67,087,526 RAC: 169,702 ![]() ![]() ![]() |
And I wish there were a way for ATLAS to identify the Windows machines that could process these successfully, and have an opt-in option for the user. I had no problems with these when they were available.I, too, would be much interested in crunching such tasks on my Windows machine (with either 3-core, 4-core or 8-core setting)! |
Send message Joined: 2 May 07 Posts: 1752 Credit: 136,505,063 RAC: 28,175 ![]() ![]() ![]() |
This idea to let 1000 Collisions running with Linux-native App is NOT against Windows, sorry. There are more Computer with running Linux-App to do this heavy work. David had a statistic for one week shown in this thread: https://lhcathome.cern.ch/lhcathome/forum_thread.php?id=4396&postid=33036#33036 |
![]() Send message Joined: 15 Jun 08 Posts: 2182 Credit: 185,876,190 RAC: 187,087 ![]() ![]() ![]() |
The idea to hand out WUs with 1000 collisions has to be planned very carefully as there are some disadvantages: 1. ATLAS (native) does not reliably accept a suspend/continue signal from the BOINC client. This must be solved first. 2. Once a host runs 1000-c-WUs it should only run those WUs. A mix of very short and very long WUs would heavily disturb the average GFLOPS calculation for that host and as a consequence would lead to utopic credit calculations and (more important) unrealistic runtime estimations. |
![]() Send message Joined: 17 Sep 04 Posts: 93 Credit: 28,760,845 RAC: 14,092 ![]() ![]() ![]() |
This idea to let 1000 Collisions running with Linux-native App is NOT against Windows, sorry. OK, I see your point. Whatever works best for the project is OK with me. Regards, Bob P. |
![]() ![]() Send message Joined: 24 Oct 04 Posts: 1037 Credit: 48,617,539 RAC: 1,022 ![]() ![]() |
over night 8 Longrunners have been finished and succesfull validated I have got several of those over at -dev with those monster sized Atlas tasks (over 5000 credits each) Only problem is the d/l of those tasks is over 426MB per task so multiply that by 10 and you can imagine how long it takes to just d/l the tasks and they run Valids much faster than the d/l time. I used up ALL of my high-speed ISP data d/l for the month in 4 days so I have the next 26 days running at snail speed. (nothing like a 2 page thread) Volunteer Mad Scientist For Life |
Send message Joined: 2 May 07 Posts: 1752 Credit: 136,505,063 RAC: 28,175 ![]() ![]() ![]() |
Only problem is the d/l of those tasks is over 426MB per task so multiply that by 10 and you can imagine how long it takes to just d/l the tasks and they run Valids much faster than the d/l time. This 425 MByte are for 200 Events at the moment! You can use this up to thursday only in -dev. |
Send message Joined: 5 Apr 15 Posts: 18 Credit: 5,910,849 RAC: 0 ![]() ![]() |
Hi, I think it's a good idea indeed, it's similar to ClimatePrediction which I also run. However, please don't run it on Ubuntu. I installed it on Windows 10 and it conflicted straight away with LHC and VirtualBox. I had to uninstall Ubuntu again and my system has since become much more unstable, prompting me to reboot my system every 3 days or otherwise risk of crashing it. Something which GPUGrid really doesn't like and results in lost WU's (which last around 6-9 hours) and it's a shame losing those if you're at 95 %... Thanks to take that into consideration ! |
©2023 CERN