Percent Complete, Літопис Налаштування

[Paul B.Atton]

Невеличкі сходинкі у проекті. Літопис:

Feb 23 2006 Percent Complete: 0.300%

Dec 23 2008 Percent Complete: 0.550%

Jan 04 2009 Percent Complete: 0.555%
Feb 04 2009 Percent Complete: 0.567%
Mar 04 2009 Percent Complete: 0.580%
Apr 04 2009 Percent Complete: 0.593%
May 04 2009 Percent Complete: 0.600%
July 15 2009 Percent Complete: 0.633%
Aug 29 2009 Percent Complete: 0.650%

Mar 15 2010 Percent Complete: 0.733%
Nov 27 2010 Percent Complete: 1.210%
Dec 12 2010 Percent Complete: 1.250%

Nov 23 2011 Percent Complete: 2.001%

May 11 2012 Percent Complete: 2.350%

Це повідомлення відредагував Rilian: May 14 2012, 11:01

[Paul B.Atton]

Percent Complete: 0.710%

[Paul B.Atton]

Percent Complete: 0.745%

[Paul B.Atton]

Percent Complete: 0.755%

[Alexis Kravtchenko]

Вау

Percent Complete: 1.009%
Time Working: 2,831 days

[Paul B.Atton]

The odds are 1 in 47,975 that we will wrap this thing
up in the next 24 hours. (This also means that we'll
hit 100% in 47,975 days at yesterday's rate.)

[Paul B.Atton]

Aggregate Statistics

Total Blocks to Search: 1,099,511,627,776
Total Blocks Tested: 13,306,237,801
Overall Rate: 53 Blocks/sec
Total Keys to Search: 4,722,366,482,869,645,213,696
Total Keys Tested: 57,149,856,188,093,956,096
Overall Rate: 226,836,992,059 Keys/sec
Percent Complete: 1.210%
Time Working: 2,916 days

The odds are 1 in 152,664 that we will wrap this thing
up in the next 24 hours. (This also means that we'll
hit 100% in 152,664 days at yesterday's rate.)

[Paul B.Atton]

Aggregate Statistics
Total Blocks to Search: 1,099,511,627,776
Total Blocks Tested: 13,741,247,925
Overall Rate: 54 Blocks/sec
Total Keys to Search: 4,722,366,482,869,645,213,696
Total Keys Tested: 59,018,210,444,102,860,800
Overall Rate: 233,053,954,077 Keys/sec
Percent Complete: 1.250%
Time Working: 2,931 days

Current Information

29,424,993 Blocks were completed yesterday (0.002676% of the keyspace)(0.002710% of the remaining keyspace)
at a sustained rate of 341 Blocks/sec.

126,379,382,620,028,928 Keys were completed yesterday (0.002676% of the keyspace)(0.002710% of the remaining keyspace)
at a sustained rate of 1,462,724,335,880 Keys/sec.

The odds are 1 in 36,900 that we will wrap this thing
up in the next 24 hours. (This also means that we'll
hit 100% in 36,900 days at yesterday's rate.)

There have been 85,128 participants
since the beginning of this project.
3,469 of them were active yesterday
and of those, 19 were brand-new participants.

There are 4,928 registered teams.
508 of them submitted work units yesterday.
(0 of them are brand new!)

[Paul B.Atton]

Aggregate Statistics
Total Blocks to Search: 1,099,511,627,776
Total Blocks Tested: 14,424,191,371
Overall Rate: 57 Blocks/sec
Total Keys to Search: 4,722,366,482,869,645,213,696
Total Keys Tested: 61,951,430,209,690,402,816
Overall Rate: 242,896,491,274 Keys/sec
Percent Complete: 1.312%
Time Working: 2,952 days



Current Information

51,786,736 Blocks were completed yesterday (0.004710% of the keyspace)(0.004772% of the remaining keyspace)
at a sustained rate of 599 Blocks/sec.

222,422,337,486,585,856 Keys were completed yesterday (0.004710% of the keyspace)(0.004772% of the remaining keyspace)
at a sustained rate of 2,574,332,609,798 Keys/sec.

The odds are 1 in 20,953 that we will wrap this thing
up in the next 24 hours. (This also means that we'll
hit 100% in 20,953 days at yesterday's rate.)

There have been 85,481 participants
since the beginning of this project.
3,260 of them were active yesterday
and of those, 14 were brand-new participants.

There are 4,928 registered teams.
474 of them submitted work units yesterday.
(0 of them are brand new!)

[Paul B.Atton]

Aggregate Statistics
Total Blocks to Search: 1,099,511,627,776
Total Blocks Tested: 22,001,965,885
Overall Rate: 78 Blocks/sec
Total Keys to Search: 4,722,366,482,869,645,213,696
Total Keys Tested: 94,497,723,923,782,696,960
Overall Rate: 333,859,480,014 Keys/sec
Percent Complete: 2.001%
Time Working: 3,276 days


Current Information

22,104,012 Blocks were completed yesterday (0.002010% of the keyspace)(0.002051% of the remaining keyspace)
at a sustained rate of 256 Blocks/sec.

94,936,008,650,391,552 Keys were completed yesterday (0.002010% of the keyspace)(0.002051% of the remaining keyspace)
at a sustained rate of 1,098,796,396,417 Keys/sec.

The odds are 1 in 48,747 that we will wrap this thing
up in the next 24 hours. (This also means that we'll
hit 100% in 48,747 days at yesterday's rate.)

There have been 89,815 participants
since the beginning of this project.
2,416 of them were active yesterday
and of those, 10 were brand-new participants.

There are 4,945 registered teams.
455 of them submitted work units yesterday.
(0 of them are brand new!)

[nikelong]

Форматирование по центру - говно.

[Death]

Andrew Hime <@verizon.net>

On August 26th, 2010, distributed.net's RC5-72 effort reached 1% completion - an effort that took 2824 days, approximately 7.7 years. At the time, I did some quick math and predicted that we would reach 2% completion by February 4th, 2012.

We got there last night, November 21st. A workload that I figured to take 1.4 years took approximately 1.2.

It took 3276 days to do 1% of the RC5-72 keyspace - a time of almost 9 years. At the current keyrate, we will complete 100% of the keyspace in
136.5 years. At the current keyrate, we will reach 3% completion in approximately 1.4 years, or around April 10th, 2013.

I did some rough math (back of napkin kind of stuff). Assuming that the keyrate doubles approximately every 18 months (which, ignoring the introduction of the Stream client, still seems valid), we will reach 100% completion within 9.3 years.

So, somewhere between 9 and 137 years to go. Given the lag time after
OGR-27 completes (somewhere between 1.5-4.5 years from now) and before the next OGR project starts, those numbers are likely on the high side.

***

I've maintained the formatting from my previous post on this subject, now some commentary:

About the Stream clents - Windows Stream has been the #1 client for quite a while now. A few months back, they accounted for more than half the total workload ever done. A few days ago, they accounted for double the workload of the #2 platform - Windows x86.

There are now 64-bit cores available for RC5. While they are not as marked an improvement in speed as OGR, one no longer has to choose projects based on "bitness", and they do provide a small speed increase over 32-bit. When people argue against doing a 64-bit version of a program, I enjoy having something to point to that shows there are benefits other than memory addressing (not to mention SSE2 and the like).

The growing prevalence of real GPUs (not Intel's solution) and of multicore computing has made solving these problems very viable. Just by way of example, my work computer (yay working!) was recently upgraded from some horrible Pentium D/Pentium 4 thing to a Core i5 running at 3.3 Ghz. With 4 cores, it processes OGR at approximately 230 Mnodes/s - a score not much lower than my Core i7-920 (2.6 Ghz) at home. And the i5 is only running 32 bit Windows XP. So things are definitely looking up.

Goals we should probably start working on now:

Short term:
upgrading 32-bit clients to 64-bit - with the increased speeds and the fact that most every shipping computer is running 64-bit OS, I'm surprised that the 64-bit clients are not gaining on 32-bit faster

Long term:
Given the institutional slowness d.net is well-known for, we should probably start talking NOW about what projects will come after RC5-72 and OGR-27... and also start work on a v3 client, which appears to have long ago been abandoned. The primary feature I'd be looking for is better granularity of stats (another abandoned project). Given the prevalence of broadband and the low overhead cost, the data being shipped back to d.net should probably be reporting back more information, like client configuration (ie processor type and speed and such). I had a laptop stolen a few years back and inquired about dnetc phoning home. I received a response that an old client had phoned home.
When I inquired further, I was met with stony silence, which is par for the course. (Of course, these features could be made opt-in or opt-out with a warning on initial configuration.) Another feature that is sorely
needed: buffer file combination/flexibility. I have to fetch/flush by mail at work, and having to juggle these files is really nonsensical, among other things.

See you at 3%!

***

Old predictions:

Approximate completion of OGR-27: 2014-2018 Approximate completion of RC5-72: 2021-2152

Current predictions:

OGR-27: 2013-2016
RC5-72: 2020-2148
_______________________________________________
rc5 mailing list
rc5@lists.distributed.net
http://lists.distributed.net/mailman/listinfo/rc5

[Rilian]

Aggregate Statistics
Total Blocks to Search: 1,099,511,627,776
Total Blocks Tested: 25,836,340,616
Overall Rate: 87 Blocks/sec
Total Keys to Search: 4,722,366,482,869,645,213,696
Total Keys Tested: 110,966,237,994,036,494,336
Overall Rate: 372,593,982,670 Keys/sec
Percent Complete: 2.350%
Time Working: 3,447 days

[Death]

бесполезность этого проекта наводит на меня ужас

примерно как в 18 лет понимаешь что папа не нужен

[Rilian]

Death, угу. уже би інопланетян давно нашлі

[egorio]

Она та же полезна, как и все другие проекты