| Author |
Message |
|---|
|
|
|
Most of the work units i have recieved so far have stated they would take about 3hrs to do. Now i have just recieved a block of them that say 18:30:29. Are 18:30 hour work units going to be normal from now on???????
|
|
|
 RyvrVolunteer tester
Send message
Joined: 27 Oct 03
Posts: 5
Credit: 355,544
RAC: 33
|
|
Ya just got WU's??? I thought the server was still down. I want some!!!
|
|
|
|
|
|
On one of my slower machines they are showing 192 hours.
|
|
|
|
|
|
I should have been more specific. I usually run thru the 3hr ones in about 2:30hrs . What i was trying to ask was much larger workunits going to be the norm. I thought i had read that it would alocate according to system speed and ram, but i cant find where i read it. so if i have and athlon 3200 and 1.5gigs of ram, are my work units going to be larger with bionic than they were with s@h1. Thanks for any answer you may have.
|
|
|
|
|
|
> On one of my slower machines they are showing 192 hours.
==========
hehe, well you should only need 1 WU every 8 days then John, more WU's for the rest of us then ... ;)
|
|
|
TobyVolunteer tester
Send message
Joined: 26 Oct 00
Posts: 1001
Credit: 5,536,461
RAC: 0
|
|
Bill, I don't think seti@home is currently using variable sized work units. BOINC is capable of handling this but any given project obviously doesn't have to use it. I am not seeing any change in my expected completion time. I suspect your client re-ran its benchmarks (as it does every few days) and for some reason got different benchmark results. Has the actual time to complete a work unit changed? I would try running the benchmarks manually and see if that does anything.
|
|
|
|
|
|
possible Time on a 486 DX 2 Prozessor System i think
[/url] [/url] |
|
|
|
|
|
> possible Time on a 486 DX 2 Prozessor System i think
Hey Guido, I have one of those. I only retired it about 6 months ago from Seti 1. Took 6.5 days to run one work unit :-o
Darren
 |
|
|
|
|
|
Hey Guys,
My workunits normaly need approx 3:30 hours which is also the shown completion time. Now I've got also some WU's with a strange approx completion time of 23 hours. And my client didn't went any new benchmark test yet.
|
|
|
|
|
|
On my machine the "long" work units are exactly 6 times the length reported for the normal WU's to the second.
Is that the same for everybody else?
Is this a way of stopping WU download? I guess now you wont hit your low water mark on the cache until your into the long units so preventing you system from downloading any more units for quite some time.
One thought is are the units really that long or have the Seti team some way of making your system think they are 6 times bigger to prevent your system requesting more work?
Regards
Neil
|
|
|
|
|
|
Same here !!!
All WU I have received had estimated time to complition of 8 hours although
it takes about 5 hours. Now I have received one of a kind.
53 hours !!!!!!!!! Can't wait to run that one and see...
Could it be some seti 2 tests ???
|
|
|
|
|
|
> On my machine the "long" work units are exactly 6 times the length reported
> for the normal WU's to the second.
>
> Is that the same for everybody else?
Mine are a bit less than 6 times. More like 5x and some change.
> Is this a way of stopping WU download? I guess now you wont hit your low water
> mark on the cache until your into the long units so preventing you system from
> downloading any more units for quite some time.
Could be.
> One thought is are the units really that long or have the Seti team some way
> of making your system think they are 6 times bigger to prevent your system
> requesting more work?
I read in another post that they actually run the same amount of time as your normal WUs.
<a> [/url] |
|
|
|
|
|
OOPS High Speed WU Killer ;-)))
[/url] [/url] |
|
|
|
|
|
Just had a look at the WU files and they are all 356 Kb in size.
I suppose that my 53 hours to completion WU would have been
much bigger. No ! My guessing is it's just to prevent low water
mark and sending request all the times.
|
|
|
|
|
|
Hi Kleine
[/url] [/url] |
|
|
|
|
|
One could try to change the values in teh client_stat.xml file.
for a "normal" wu the values are:
|workunit|
|name|01ja04aa.2129.26368.709636.238|/name|
|app_name|setiathome|/app_name|
|version_num|308|/version_num|
|command_line||/command_line|
|env_vars||/env_vars|
|rsc_fpops_est|27924800000000.000000|/rsc_fpops_est|
|rsc_fpops_bound|446797000000000.000000|/rsc_fpops_bound|
|rsc_memory_bound|33554422.000000|/rsc_memory_bound|
|rsc_disk_bound|500000.000000|/rsc_disk_bound|
|/workunit|
and for the mystery one:
|workunit|
|name|11ja04aa.29978.26002.92308.94|/name|
|app_name|setiathome|/app_name|
|version_num|308|/version_num|
|command_line||/command_line|
|env_vars||/env_vars|
|rsc_fpops_est|167548800000000.000000|/rsc_fpops_est|
|rsc_fpops_bound|2680782000000000.000000|/rsc_fpops_bound|
|rsc_memory_bound|33554422.000000|/rsc_memory_bound|
|rsc_disk_bound|500000.000000|/rsc_disk_bound|
|/workunit|
so it seems to be the values for "rsc_fpops_est" and "rsc_fpops_bound" resbonsible for the estimated completion time. so one may change the values of the abnormal one to the normal values. perhaps this should alter the estimated completion time after a restart of boinc.
|
|
|
|
|
|
I just picked up my first "BIG ONES" 3 WU's came in overnight with 31:00 hour completion times each... Wow.
I do my regular ones in about 2:00 hours and they are always estimated at around 5:11 so maybe I'll get these 31 hour ones done in about 13 or so I'd guess. (if it works that way)
I guess we'll have to just wait and see.
|
|
|
|
|
|
The "super" WU I got last night processed in my normal amount of time - 3h 30m
I think the completion times are just a little messed at the beginning. I got a bunch of new ones saying 4h 44m now.
- PyroFox
 |
|
|
