Page 1 of 1
timing a work unit
Posted: Fri Mar 14, 2025 6:40 pm
by whocrazy
Hi. Just out of curiosity, I am doing project 8806, which takes just over 5 hours to complete on my machine. I am really interested in what sort of times other people get on their machine with this project.
Thanks.
Re: timing a work unit
Posted: Fri Mar 14, 2025 6:50 pm
by Joe_H
Re: timing a work unit
Posted: Fri Mar 14, 2025 7:05 pm
by Joe_H
I looked at older logs on one of my machines, ~14:45 to complete on a Hackintosh with an i7-7700K processor using 4 CPU threads running macOS 10.13.6 for a Project 18806 WU.
Re: timing a work unit
Posted: Fri Mar 14, 2025 11:07 pm
by whocrazy
whoops sorry, yes, I meant 18806
wow. 14:45? I'm guessing you mean 14 minutes and 45 seconds? grrrrr. I'm jealous!
Re: timing a work unit
Posted: Sat Mar 15, 2025 2:19 am
by Joe_H
Nope. 14 hours and 45 minutes. Used to get these WUs, but currently doing beta projects and haven't seen any in abut a month.
Re: timing a work unit
Posted: Fri Mar 21, 2025 4:12 am
by whocrazy
The longest work units I've ever had on this new machine took 14 hours. I've not seen any of those for quite a few weeks. I forget the number of the project that it consisted of.
Now the longest I've been getting lately is 8 to 9 hours.
Re: timing a work unit
Posted: Fri Mar 21, 2025 4:38 am
by Joe_H
I just remember starting out nearly 20 years ago and WUs taking 7-10 days to complete, have no memory of how many points they were given. Not many though. Still recall having my first dual core machine and being able to see the speedup.
Re: timing a work unit
Posted: Fri Mar 21, 2025 9:54 am
by arisu
I got a list of hours that it took to complete each generation (with some duplicates from expired timeouts) of run 88, clone 14 for project 18806 (394 as of this post). Here are some basic stats using R:
Code: Select all
> h <- read.csv('hours.txt', header=F)
> summary(h)
V1
Min. : 2.57
1st Qu.:11.46
Median :18.66
Mean :21.35
3rd Qu.:27.11
Max. :71.63
> sd(h[,])
[1] 13.12557