Message boards : Number crunching : Some requests/advices for the Python app
Author | Message |
---|---|
[VENETO] boboviz Send message Joined: 1 Dec 05 Posts: 1990 Credit: 9,487,316 RAC: 12,258 |
I try to aggregate some requests, that are scattered in different place, for the new app: - longer deadline for the Py wsus. Only 2 days is too little time - introduce the multi-attach disk function, to reduce space and usage of our disks - introduce the possibility to choose the Py app in our user's profile - not to download EVERY time the .vdi file (over 5gb) I'm pretty sure the admins won't read this thread, but there's no harm in trying. If you have other requests, please write here |
[VENETO] boboviz Send message Joined: 1 Dec 05 Posts: 1990 Credit: 9,487,316 RAC: 12,258 |
Aaaannnnnd still NO new wrapper and continue the download of vdi files!! |
Dirk Broer Send message Joined: 16 Nov 05 Posts: 22 Credit: 3,327,412 RAC: 3,557 |
- longer deadline for the Py wsus. Only 23 hours is too little time, especially when the predicted runtime is two days |
Grant (SSSF) Send message Joined: 28 Mar 20 Posts: 1667 Credit: 17,439,160 RAC: 24,424 |
Or maybe just a better prediction of the runtime, which appears to be around 2.5hrs for an average system, 4.5hrs for a more basic one.- longer deadline for the Py wsus. Only 23 hours is too little time, especially when the predicted runtime is two days The deadlines are 2 days. If it takes more than 2 days to do 8 hours of work (the default runtime) then Rosetta just isn't the project for you. Grant Darwin NT |
[VENETO] boboviz Send message Joined: 1 Dec 05 Posts: 1990 Credit: 9,487,316 RAC: 12,258 |
Or maybe just a better prediction of the runtime, which appears to be around 2.5hrs for an average system, 4.5hrs for a more basic one. Maybe a better precision will help the boinc client scheduler to download the correct number of wus... |
Grant (SSSF) Send message Joined: 28 Mar 20 Posts: 1667 Credit: 17,439,160 RAC: 24,424 |
It's been forever, but i'm pretty sure it won't make any difference. There were big issues with the initial Estimated completion time when i first joined the project- i'm pretty sure the end result was they fixed it at 8 hours (project default CPU Target time), regardless of the WU (or the Target CPU time set). Or it might have been set to the Target CPU time for that system- it's been so long i can't remember exactly what was done at the time.Or maybe just a better prediction of the runtime, which appears to be around 2.5hrs for an average system, 4.5hrs for a more basic one. It was easier to do that than fix the actual problem (by using a moving average of previously completed Tasks runtime for each application on each system). Grant Darwin NT |
[VENETO] boboviz Send message Joined: 1 Dec 05 Posts: 1990 Credit: 9,487,316 RAC: 12,258 |
Seems that the 26207 version of vboxwrapper was released (without much noise). |
Dirk Broer Send message Joined: 16 Nov 05 Posts: 22 Credit: 3,327,412 RAC: 3,557 |
Or maybe just a better prediction of the runtime, which appears to be around 2.5hrs for an average system, 4.5hrs for a more basic one.- longer deadline for the Py wsus. Only 23 hours is too little time, especially when the predicted runtime is two days I have no problem with the project, just the python vbox app. Virtual box seems to be a real pain in the ass, IMHO. |
[VENETO] boboviz Send message Joined: 1 Dec 05 Posts: 1990 Credit: 9,487,316 RAC: 12,258 |
I have no problem with the project, just the python vbox app. Virtual box seems to be a real pain in the ass, IMHO. And it's a pity. With a little effort the situation could be better... |
Message boards :
Number crunching :
Some requests/advices for the Python app
©2024 University of Washington
https://www.bakerlab.org