Next scheduled rescrape ... never
Version 2
Last scraped
Edited on 02/07/2025, 20:00:39 UTC
Fast…


I think there is now a disproportiondiscrepancy in how the realactual speed is measured, depending on the size of dp_table.bin. For example, with a 50GB database larger than 50GB, the speed reaches into the petabytes,petabits per second in hops similar to Keyhunt. This is especially noticeable when dealing with a smallworking on smaller puzzles, such as Puzzle 55, 60, or 66, if the database is "too large" for a specific range.
Version 1
Scraped on 25/06/2025, 20:05:45 UTC
Fast…


I think there is now a disproportion in how the real speed is measured. For example, with a 50GB database, the speed reaches into the petabytes, similar to Keyhunt. This is especially noticeable when dealing with a small number of puzzles, such as Puzzle 66, if the database is too large.
Original archived Re: Mark1 - pollard rho implementation (38 minutes for 80 bits solving on CPU)
Scraped on 25/06/2025, 20:00:58 UTC
Fast…


I think there is now a disproportion in how the real speed is measured. For example, with a 50GB database, the speed reaches into the petabytes, similar to Keyhunt. This is especially noticeable when dealing with a small number of puzzles, such as Puzzle 66, if the database is too large.