My Boinc 5.5.4 (Alpha version, rather unstable, yes i am an alpha tester) just requested work from Einstein.
2006-06-27 23:26:28 [Einstein@Home] Sending scheduler request to http://einstein.phys.uwm.edu/EinsteinAtHome_cgi/cgi
2006-06-27 23:26:28 [Einstein@Home] Reason: To fetch work
2006-06-27 23:26:28 [Einstein@Home] Requesting 4231351227038568400000000000000 seconds of new work
2006-06-27 23:26:28.0156 [DEBUG_HTTP ] HTTP_OP::init_post(): 00524840 io_done 0
2006-06-27 23:26:48 [Einstein@Home] Scheduler request succeeded
How many seconds? :-)
(According to my Windows calculator this comes out at: 134,175,267,219,640,043,125,317.09791984 years of work... )
Suffice to say, if I had gotten it, I would be crunching Einstein alone. ;-)
And all that on a connect to of 0.5 days. Marvellous stuff this, computers.
Copyright © 2024 Einstein@Home. All rights reserved.
How many years of work?
)
Well, you do call yourself ageless, right?? :).
Cheers,
Gary.
RE: RE: (According to my
)
That is an awfully big number! :-)
A fairly liberal data type chosen there, and probably no bounds checking.
Cheers, Mike.
I have made this letter longer than usual because I lack the time to make it shorter ...
... and my other CPU is a Ryzen 5950X :-) Blaise Pascal
RE: A fairly liberal data
)
You can say that again. I got 9 slices of my big H1 result, all of which take around 13 hours to crunch. Also on that 0.5 day cache. So of course I am running in EDF mode.
RE: RE: (According to my
)
...after that time, you will know the results of colliding black holes and neutron stars...
...after using akosf optimized S4 app, your '' (within client_state.xml) should have been dropped to something between 0.15 and 0.2 ...
And with this factor and the official S5 app BOINC client is requesting much to many WUs...
Udo
Udo
RE: ...after using akosf
)
Nice try. :-)
But my DCF is at this moment at:
Result duration correction factor 0.895798
Around the time I got work it was at 1. A reset or two in BOINC will do that to you. :-)