Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
![]() |
World Community Grid Forums
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
No member browsing this thread |
Thread Status: Active Thread Type: Sticky Thread Total posts in this thread: 1840
|
![]() |
Author |
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Backblaze recently published an updated 135TB design of their storage pod – and we are naturally all ear...
http://blog.backblaze.com/2011/07/20/petabyte...816486339#f391f3923aa098c |
||
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Nice of Backblaze to indicate their drive vendor given their quantifiable experience. Although it is not one I've used to date, on the other hand I've got a couple thousand dollars in failed hard drives from the traditionally accepted "major" vendors sitting on this, that and the other surface waiting for me to get the ambition to deal with their customer "service"...and packaging...and shipping...
All too many of which were DOA right out of the antistatic wrap (unless I mistook funereal shrouds for antistatic wrap?). Time for a change, perhaps, and I find Backblaze's petabytes of experience to be...reassuring. |
||
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
|
||
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
We implemented an in-house result validation which will allow us to get rid of the redundancies caused by the wingman-system. We forwarded it to our friends at IBM yesterday and it can hopefully go live soon (i.e., after some testing). This will essentially double the productivity of CEP2!
![]() |
||
|
Falconet
Master Cruncher Portugal Joined: Mar 9, 2009 Post Count: 3295 Status: Offline Project Badges: ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
We implemented an in-house result validation which will allow us to get rid of the redundancies caused by the wingman-system. We forwarded it to our friends at IBM yesterday and it can hopefully go live soon (i.e., after some testing). This will essentially double the productivity of CEP2! ![]() So there will be only one copy per work unit? That's great!! AMD Ryzen 5 1600AF 6C/12T 3.2 GHz - 85W AMD Ryzen 5 2500U 4C/8T 2.0 GHz - 28W AMD Ryzen 7 7730U 8C/16T 3.0 GHz |
||
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Exactly
![]() |
||
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
We implemented an in-house result validation which will allow us to get rid of the redundancies caused by the wingman-system. We forwarded it to our friends at IBM yesterday and it can hopefully go live soon (i.e., after some testing). This will essentially double the productivity of CEP2! Is your approach unique to CEP2, or applicable across all things Grid which require a wingman?![]() I have a tendency towards histrionics, I suspect, but a 50% or greater reduction in the amount of time it takes to solve problems of the magnitude the grid is being applied towards is sneaking up on descriptives like "world-changing". |
||
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Hello ibsteve2u,
Validation without repetition is always project-specific, though there are numerous examples to provide helpful hints. Lawrence |
||
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
CEP2 has passed 4,500 years of computing time on the World Community Grid – all made possible by the WCG crunchers! A big THANK YOU to all of you!
https://secure.worldcommunitygrid.org/stat/viewProject.do?projectShortName=cep2 |
||
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Dear ibsteve2u,
sorry - it's only gonna work for CEP2. But other projects may want to have a closer look whether there are cheaper ways to ensure the validity of the obtained results. Best wishes, Your Harvard CEP team |
||
|
|
![]() |