Message boards :
Xtrack/SixTrack :
Xtrack (Xboinc)
Message board moderation
Previous · 1 . . . 6 · 7 · 8 · 9 · 10 · 11 · 12 · Next
| Author | Message |
|---|---|
|
Send message Joined: 22 Mar 17 Posts: 76 Credit: 27,457,157 RAC: 110,143  
|
Yay initial ETA of 149 days |
|
Send message Joined: 5 Apr 25 Posts: 51 Credit: 824,170 RAC: 22,683   
|
Yay initial ETA of 149 days Got tasks on another laptop that I can access with TeamViewer and I see an estimate of 22 hours. After 7 minutes I see 0,5% progress which is consistent with the total runtime estimate. 
|
|
New member Send message Joined: 3 Oct 25 Posts: 3 Credit: 544,830 RAC: 22,997 |
The estimated runtime for these tasks on my 7950X is over 2000 hours121 days on my 3900X which hadn't seen Xtrack before. The tasks don't seem to report progress so the remaining time doesn't drop below inf until the tasks finish. Full to the brim in one moment, empty in the next. |
 Conan Send message Joined: 6 Jul 06 Posts: 111 Credit: 1,082,685 RAC: 20,441 |
Hmm curious, estimate is 135 days but due in 5 days, does not compute. These latest work units may have the wrong settings Conan |
|
Send message Joined: 5 Apr 25 Posts: 51 Credit: 824,170 RAC: 22,683
|
Got tasks on another laptop that I can access with TeamViewer and I see an estimate of 22 hours. One of them just finished after 3 hours. Probably ran out of particles as Carlo suggested. The other 17 are all showing the same progress and remaining estimate.
|
|
New member Send message Joined: 3 Oct 25 Posts: 3 Credit: 544,830 RAC: 22,997 |
Hmm curious, estimate is 135 days but due in 5 days, does not compute.Fortunately BOINC is not that smart so it does compute. After finishing some tasks my estimates are down from 121 days to 96 minutes which looks reasonable. |
|
Send message Joined: 22 Mar 17 Posts: 76 Credit: 27,457,157 RAC: 110,143
|
Some of the tasks progress the %, others jump from 0.10 % to completion. From the tasks I've been able to watch, its ones with flat in the name that jump to 100%. Due to the crazy high ETA, the client will not ask for more work as it's expecting the tasks to run basically forever. Tasks with round in the name only have 500 FLOPS vs 500k FLOPS with flat in the name so the % completion actually works even with similar run time. camontan__tune_scan_start_of_collapse_flat_scan_195__ScanShort_2_1__Hm6gxUEpNDDl_0 |
|
Ravkin Send message Joined: 2 Dec 09 Posts: 2 Credit: 2,767,271 RAC: 19,827 |
I've been trying to get these new xtrack tasks for a week now, I updated both virtualbox and boinc because the server complaining about it but it was already installed. Do they come with some extra caviat I don't know about? Now the virtualbox issue is gone, shouldn't even cause a problem since xtrack is not using virtual box, but it seems that the server is still rejecting to send me new tasks. 2025. 10. 04. 15:01:21 | LHC@home | Requesting new tasks for CPU 2025. 10. 04. 15:01:22 | LHC@home | Scheduler request completed: got 0 new tasks 2025. 10. 04. 15:01:22 | LHC@home | No tasks sent 2025. 10. 04. 15:01:22 | LHC@home | No tasks are available for XTrack 2025. 10. 04. 15:01:22 | LHC@home | Project requested delay of 6 secondsAt the time of writing there are 51738 tasks in the queue. At this point I'm clueless why I'm unable to recive any xtrack task. |
|
Send message Joined: 5 Apr 25 Posts: 51 Credit: 824,170 RAC: 22,683
|
Some of the tasks progress the %, others jump from 0.10 % to completion. From the tasks I've been able to watch, its ones with flat in the name that jump to 100%. Due to the crazy high ETA, the client will not ask for more work as it's expecting the tasks to run basically forever. Tasks with round in the name only have 500 FLOPS vs 500k FLOPS with flat in the name so the % completion actually works even with similar run time. I finally ran into this issue when a laptop running Linux Mint got a few tasks. ETA is 126 days. Similarly named "flat" tasks are estimated at 22-24 hours on Windows and actually run 3-5, possibly longer when more particles survive.
|
 Send message Joined: 15 Jun 08 Posts: 2679 Credit: 286,639,849 RAC: 99,609  |
... the server is still rejecting to send me new tasks. As long as it is marked as beta app you need to allow beta work at your prefs page. Be aware that this may cause unexpected behaviour. |
|
Ravkin Send message Joined: 2 Dec 09 Posts: 2 Credit: 2,767,271 RAC: 19,827 |
Ah thank you so much! |
|
Send message Joined: 16 Nov 17 Posts: 15 Credit: 92,768 RAC: 100 |
I've got a task that is due October 10 and has an estimated time to completion of 49 days. Will this rectify itself and be done much sooner than in the third week of November? If not, it will miss the deadline by well over a month. |
|
Conan Send message Joined: 6 Jul 06 Posts: 111 Credit: 1,082,685 RAC: 20,441 |
I've got a task that is due October 10 and has an estimated time to completion of 49 days. Will this rectify itself and be done much sooner than in the third week of November? If not, it will miss the deadline by well over a month. It wont take that long, probably around 4 hours or so, the estimates are just way off but will come down as more work units get done by yourself. Conan |
|
Send message Joined: 5 Apr 25 Posts: 51 Credit: 824,170 RAC: 22,683
|
Some of the tasks progress the %, others jump from 0.10 % to completion. From the tasks I've been able to watch, its ones with flat in the name that jump to 100%. Due to the crazy high ETA, the client will not ask for more work as it's expecting the tasks to run basically forever. Tasks with round in the name only have 500 FLOPS vs 500k FLOPS with flat in the name so the % completion actually works even with similar run time. Can confirm that the Linux tasks also run 2-6 hours regardless of initial ETA.
|
|
Send message Joined: 2 May 07 Posts: 2276 Credit: 177,520,536 RAC: 78,666
|
https://lhcathome.cern.ch/lhcathome/result.php?resultid=427741365 <core_client_version>8.2.4</core_client_version> < Send message Joined: 7 May 08 Posts: 248 Credit: 1,809,807 RAC: 9,854 
|
Something has changed: credits awarded for the latest batch of tasks are a fraction of what was granted up until yesterday. CPU time required for 1 credit is about 500-1000 seconds which seems to be 10x as much as it used to be. The wus are a lot shorter than before... |
|
Send message Joined: 5 Apr 25 Posts: 51 Credit: 824,170 RAC: 22,683
|
Something has changed: credits awarded for the latest batch of tasks are a fraction of what was granted up until yesterday. CPU time required for 1 credit is about 500-1000 seconds which seems to be 10x as much as it used to be. Yeah, but that doesn't change the fact that we're getting 1/10th of the credits per CPU time.
|
|
Send message Joined: 22 Mar 17 Posts: 76 Credit: 27,457,157 RAC: 110,143
|
Welcome to CreditNew Wait until you run quorum = 2 tasks and your credit is 1/10th of what it should be because your wingman hasn't run benchmarks. |
|
Send message Joined: 18 Dec 14 Posts: 2 Credit: 1,164,695 RAC: 1,297 
|
Something has changed: credits awarded for the latest batch of tasks are a fraction of what was granted up until yesterday. CPU time required for 1 credit is about 500-1000 seconds which seems to be 10x as much as it used to be. WUs with CPU time 10 times less get 100 times less points: Yesterday CPU time 15,780.35 got 148.07 points Today CPU time 1,823.91 got 2.68 points |
©2025 CERN