Message boards :
Sixtrack Application :
Very long Tasks
Message board moderation
Previous · 1 · 2
| Author | Message |
|---|---|
 ritterm Send message Joined: 30 May 08 Posts: 93 Credit: 5,160,246 RAC: 0  
|
|
 Send message Joined: 15 Jun 08 Posts: 2567 Credit: 258,104,908 RAC: 118,680   |
|
|
Send message Joined: 29 Feb 16 Posts: 157 Credit: 2,659,975 RAC: 0  |
Well, GPUs are suitable for calculations that can be run in parallel. That could be the case for SixTrack only if the number of particles is kept constant with time, which implies all stable particles. But once you start hitting unstable regions of the phase space, you should switch back to regular CPUs. Knowing this point a-priori would imply also knowing the dynamic aperture, which is exactly what we are looking at... Anyway, the effort to go to GPUs is on-going, but that requires deep re-factoring of the code. It is not in our top-priority, but it is steadily progressing - no clear ETA, though...
Great job, many many thanks! |
|
ritterm Send message Joined: 30 May 08 Posts: 93 Credit: 5,160,246 RAC: 0
|
Whoa... Always a pleasure to grind it out for my favorite project... :-) |
|
Send message Joined: 2 May 07 Posts: 2255 Credit: 174,204,943 RAC: 8,340 
|
This Sixtrack(avx)-248217116 is shown with a runtime of more than 2 days for the moment (10-Time greater than normal) https://lhcathome.cern.ch/lhcathome/workunit.php?wuid=124082860 |
Magic Quantum Mechanic Send message Joined: 24 Oct 04 Posts: 1184 Credit: 56,968,484 RAC: 63,232
|
This Sixtrack(avx)-248217116 is shown with a runtime of more than 2 days for the moment (10-Time greater than normal) Those are the workspace1_HEL_Qp Sixtrack tasks taking close to 55 hours and I had 2 that just finished as Validate state - Workunit error - check skipped So after a few of those I decided against wasting 55 hours and just abort them when I see them after a reload of tasks. ( I have just one of those that only ran 16 hours but have the same Validate state) https://lhcathome.cern.ch/lhcathome/result.php?resultid=247499200 https://lhcathome.cern.ch/lhcathome/result.php?resultid=247174576 https://lhcathome.cern.ch/lhcathome/result.php?resultid=247174715 This one was instead a Exit status 196 (0x000000C4) EXIT_DISK_LIMIT_EXCEEDED Run time 16 hours 45 min 54 sec https://lhcathome.cern.ch/lhcathome/result.php?resultid=247556609 |
|
Send message Joined: 29 Feb 16 Posts: 157 Credit: 2,659,975 RAC: 0 |
The issue with those tasks has been addressed here: https://lhcathome.cern.ch/lhcathome/forum_thread.php?id=4690 We had a problem with the setting up of a bunch of simulations with 1^7 turns, and a log file was eating up all the disk quota. The user was not aware that sixtrack was producing that log file, and how to update the request. Hence, I have decided to manually attribute credit to those tasks based on the CPU time via the --credit_from_runtime option of the BOINC validator. I should have also given credit to your tasks, but I had a malformed query to the DB - now everything should be properly set, and you should see credit to those tasks. Thanks a lot in advance, Happy cruncing, A. |
|
Magic Quantum Mechanic Send message Joined: 24 Oct 04 Posts: 1184 Credit: 56,968,484 RAC: 63,232
|
The issue with those tasks has been addressed here: Thanks Alessio, Glad I stopped by here again just now to see that was taken care off. I have no problem with running long tasks as long as they end up being used after they are finished. (especially over 55 hours each) - Samson |
|
Send message Joined: 18 Dec 15 Posts: 1838 Credit: 121,602,818 RAC: 88,994
|
A few days ago, when there were Sixtrack tasks available for a short period of time, on one of my PCs I downloaded quite a a number of them, because the first few ones got ready within seconds. The other ones I downloaded turn out to be longrunners, it takes them about 10 hours to get finished (workspace2_hl14_collision_ ...). They all have deadline December 13. For sure, not all of them will get finished before that date. Question for the experts: what should I do with the tasks with are left in the queue on December 13? Would it make sense to get them crunched, anyway, although they would upload beyond the deadline? Or does it make best sense to delete them from the queue since there is no use in getting them crunched? |
|
Send message Joined: 15 Jun 08 Posts: 2567 Credit: 258,104,908 RAC: 118,680 |
As soon as the deadline (+ a short grace period) is over the server marks the tasks as lost and initiates a resend. Lost tasks don't get credits. Hence, they should be cancelled. |
 Send message Joined: 28 Sep 04 Posts: 739 Credit: 50,534,258 RAC: 33,438 
|
Does Boinc cancel tasks that have not been started at deadline? I am using BoincTasks as a Boinc Manager substitute and that happens, but I don't know if that is a feature of Boinc or BoincTasks. Tasks that are already running at deadline will continue running until they are finished. 
|
|
Send message Joined: 15 Jun 08 Posts: 2567 Credit: 258,104,908 RAC: 118,680 |
Does Boinc cancel tasks that have not been started at deadline? The project server can cancel tasks at the client that are not yet started but I'm not sure if this is the default or just an option. Tasks that are already running at deadline will continue running until they are finished. Right, but they don't get credits if they are marked as overdue at the server. |
|
Send message Joined: 28 Sep 04 Posts: 739 Credit: 50,534,258 RAC: 33,438
|
Tasks that are already running at deadline will continue running until they are finished. They might if you can return your result before the third host does.
|
©2025 CERN