Multiple VM workunits running at the same time?
-
- Brain-Bug
- Beiträge: 564
- Registriert: 26.07.2013 15:41
Re: Multiple VM workunits running at the same time?
Christian / Michael:
In:
- v1.15 (which uses VBoxWrapper 26167)
- v1.16 (which likely uses VBoxWrapper 26179)
The Progress % is not being reported correctly, and the Time Remaining (Estimated) may be showing a malformed value. These issues are happening because the "cms_vbox_job*.xml" files have a <fraction_done_filename> value of "shared/progress.txt". Per my offline testing, this needs to be changed to only be set to "progress.txt" ... and the "shared/" text needs to be removed from that xml file... and then things will work correctly. NOTE: A user should NOT try to perform these changes on their data folder, because it'll cause their tasks to abort.
Rom mentioned that he normalized this setting to remove the need for the "shared/" text, at some point. I guess he did it in a VBoxWrapper version earlier than your 2 apps, because they are both busted.
Would you guys please consider creating a new application, without "shared/", to fix this issue?
Thanks!
Jacob Klein
In:
- v1.15 (which uses VBoxWrapper 26167)
- v1.16 (which likely uses VBoxWrapper 26179)
The Progress % is not being reported correctly, and the Time Remaining (Estimated) may be showing a malformed value. These issues are happening because the "cms_vbox_job*.xml" files have a <fraction_done_filename> value of "shared/progress.txt". Per my offline testing, this needs to be changed to only be set to "progress.txt" ... and the "shared/" text needs to be removed from that xml file... and then things will work correctly. NOTE: A user should NOT try to perform these changes on their data folder, because it'll cause their tasks to abort.
Rom mentioned that he normalized this setting to remove the need for the "shared/" text, at some point. I guess he did it in a VBoxWrapper version earlier than your 2 apps, because they are both busted.
Would you guys please consider creating a new application, without "shared/", to fix this issue?
Thanks!
Jacob Klein
-
- Mikrocruncher
- Beiträge: 23
- Registriert: 15.03.2011 10:40
Re: Multiple VM workunits running at the same time?
Didn't save any of my formatting, maybe just go straight for the excel file guys.
approx -7 days Base Line + 6 mins
App version No. 1.0.2 1.15 (vbox64) 1.0.2 1.15 (vbox64) 1.0.2 1.15 (vbox64)
EXE/Process VBoxHeadless.exe VBoxHeadless.exe VBoxHeadless.exe
Elapsed Time 3725 3848:01:12 384:08:11
CPU at last checkpoint 3408:04:10 3408:04:10
CPU time 3408:15:30 3804:21:30
Time remaining 653 627:20:53 627:19:25
Percentage 85.074 85.982 85.983
App version No. 1.0.2 1.15 (vbox64) 1.0.2 1.15 (vbox64) 1.0.2 1.15 (vbox64)
EXE/Process VBoxHeadless.exe VBoxHeadless.exe VBoxHeadless.exe
Elapsed Time 201 324:31:54 324:38:53
CPU at last checkpoint 284:23:08 284:23:08
CPU time 324:31:54 284:40:58
Time remaining 2425 2366:40:33 2366:37:12
Percentage 7.674 12.059 12.063
App version No. 1.0.2 1.16 (vbox64) 1.0.2 1.16 (vbox64) 1.0.2 1.16 (vbox64)
EXE/Process VBoxHeadless.exe VBoxHeadless.exe VBoxHeadless.exe
Elapsed Time 26 150:26:43 150:33:42
CPU at last checkpoint 132:02:24 132:02:24
CPU time 150:26:43 132:19:04
Time remaining 1236 1236 1236:39:57
Percentage 0.100 0.100 0.100
If you want the data in a spreadsheet? https://www.dropbox.com/s/l088wiz4ew0sdi0/RNA.xlsx?dl=0
There was also 2 x 'vboxwrapper_26167_windows_x86_64.exe' and 1 x 'vboxwrapper_26179_windows_x86_64.exe' processes running but they do not show any noticeable CPU time.
Nope not planning on killing it off anytime soon.
Yes the remaining time does not go down.
The progress.txt result still has not reached over 0.06 so it will be interesting to see if when it hits 0.1 if the Boinc progress will start moving up then as well.
Looks like Jacob may have something too.
approx -7 days Base Line + 6 mins
App version No. 1.0.2 1.15 (vbox64) 1.0.2 1.15 (vbox64) 1.0.2 1.15 (vbox64)
EXE/Process VBoxHeadless.exe VBoxHeadless.exe VBoxHeadless.exe
Elapsed Time 3725 3848:01:12 384:08:11
CPU at last checkpoint 3408:04:10 3408:04:10
CPU time 3408:15:30 3804:21:30
Time remaining 653 627:20:53 627:19:25
Percentage 85.074 85.982 85.983
App version No. 1.0.2 1.15 (vbox64) 1.0.2 1.15 (vbox64) 1.0.2 1.15 (vbox64)
EXE/Process VBoxHeadless.exe VBoxHeadless.exe VBoxHeadless.exe
Elapsed Time 201 324:31:54 324:38:53
CPU at last checkpoint 284:23:08 284:23:08
CPU time 324:31:54 284:40:58
Time remaining 2425 2366:40:33 2366:37:12
Percentage 7.674 12.059 12.063
App version No. 1.0.2 1.16 (vbox64) 1.0.2 1.16 (vbox64) 1.0.2 1.16 (vbox64)
EXE/Process VBoxHeadless.exe VBoxHeadless.exe VBoxHeadless.exe
Elapsed Time 26 150:26:43 150:33:42
CPU at last checkpoint 132:02:24 132:02:24
CPU time 150:26:43 132:19:04
Time remaining 1236 1236 1236:39:57
Percentage 0.100 0.100 0.100
If you want the data in a spreadsheet? https://www.dropbox.com/s/l088wiz4ew0sdi0/RNA.xlsx?dl=0
There was also 2 x 'vboxwrapper_26167_windows_x86_64.exe' and 1 x 'vboxwrapper_26179_windows_x86_64.exe' processes running but they do not show any noticeable CPU time.
Nope not planning on killing it off anytime soon.
Yes the remaining time does not go down.
The progress.txt result still has not reached over 0.06 so it will be interesting to see if when it hits 0.1 if the Boinc progress will start moving up then as well.
Looks like Jacob may have something too.
- Dateianhänge
-
- RNA.xlsx
- (10.03 KiB) 254-mal heruntergeladen
-
- Brain-Bug
- Beiträge: 564
- Registriert: 26.07.2013 15:41
Re: Multiple VM workunits running at the same time?
Thanks for your info, Ian!
For the v1.16 task, I would expect it to keep showing 0.1% progress throughout the entire task, even when progress.txt has a higher value. For all 3 of your tasks, just keep monitoring progress.txt... and if progress.txt eventually gets stuck on the value 0.98765, don't get discouraged, just let it continue to run to completion. And make sure it checks in with the server, at least every 10 days, to update the server-side deadline and prevent your task from expiring
We'll need a v1.17, for future tasks, to correct the progress % problems that exist in v1.16 and v1.15.
Hopefully the admins can get to it soon!
Regards,
Jacob Klein
For the v1.16 task, I would expect it to keep showing 0.1% progress throughout the entire task, even when progress.txt has a higher value. For all 3 of your tasks, just keep monitoring progress.txt... and if progress.txt eventually gets stuck on the value 0.98765, don't get discouraged, just let it continue to run to completion. And make sure it checks in with the server, at least every 10 days, to update the server-side deadline and prevent your task from expiring
We'll need a v1.17, for future tasks, to correct the progress % problems that exist in v1.16 and v1.15.
Hopefully the admins can get to it soon!
Regards,
Jacob Klein
-
- Admin
- Beiträge: 1920
- Registriert: 23.02.2010 22:12
Re: Multiple VM workunits running at the same time?
I don't know If I'm able to sign the new job.xml file and release a new version this week (the key may be on another PC I currently don't have access to). I'll do it as soon as possible. Thanks for finding that out.
-
- Brain-Bug
- Beiträge: 564
- Registriert: 26.07.2013 15:41
Re: Multiple VM workunits running at the same time?
You're welcome. Sounds good. Thank you.
- Gibson Praise
- Mikrocruncher
- Beiträge: 16
- Registriert: 31.01.2016 01:53
- Wohnort: Hiding from the Syndicate
- Kontaktdaten:
Re: Multiple VM workunits running at the same time?
No such luckIanEdwardJames hat geschrieben: The progress.txt result still has not reached over 0.06 so it will be interesting to see if when it hits 0.1 if the Boinc progress will start moving up then as well.
-
- Brain-Bug
- Beiträge: 564
- Registriert: 26.07.2013 15:41
Re: Multiple VM workunits running at the same time?
For those tracking this thread...
Christian mentioned that he updated the application to v1.17, which includes an updated VBoxWrapper, and a new vbox.job file that should allow progress to report correctly in the UI, instead of constantly reporting 0.1% progress. Prior versions are still valid for getting work done, though, so DON'T abort your 1.14/1.15/1.16 tasks!
Note: If progress appears to get stuck at 98.765%, it actually is still progressing, DON'T abort it - the estimate was just way too low, but your work is still valid, so don't abort it! You can make sure it is progressing because the progress.txt file's modified date should be getting updated, even if the value inside stays at 0.98765. If you want to know an even crazier way to verify progress, you can PM me and I'll explain a riskier technical way.
Thanks,
Jacob
Christian mentioned that he updated the application to v1.17, which includes an updated VBoxWrapper, and a new vbox.job file that should allow progress to report correctly in the UI, instead of constantly reporting 0.1% progress. Prior versions are still valid for getting work done, though, so DON'T abort your 1.14/1.15/1.16 tasks!
Note: If progress appears to get stuck at 98.765%, it actually is still progressing, DON'T abort it - the estimate was just way too low, but your work is still valid, so don't abort it! You can make sure it is progressing because the progress.txt file's modified date should be getting updated, even if the value inside stays at 0.98765. If you want to know an even crazier way to verify progress, you can PM me and I'll explain a riskier technical way.
Thanks,
Jacob
-
- Mikrocruncher
- Beiträge: 23
- Registriert: 15.03.2011 10:40
Re: Multiple VM workunits running at the same time?
Thanks dude.