News for hackers. Stuff that matters.

A comment on Crowdsourcing Bruteforcing: Help me win the EngineYard challenge. Parent comment

Re:Crowdsourcing Bruteforcing: Help me win the EngineYard ch... by Periodic on Monday July 20, 2009 @04:14PM (#715077)
It's going to be a lot slower, particularly with the goal of not slowing down a person's browser. By default, at least for me, their page is doing 1 hash per 200ms, or 5/second.

On the other hand, a quick Haskell implementation using Data.Digest.Pure.SHA is doing about 6,000 hashes per second (might have been 8000, I forget now) per core on an Intel(R) Core(TM)2 Duo CPU E6750 @ 2.66GHz

So you're looking at 1000 people to equal one core of a decent desktop. It's certainly an interesting approach, and has a lot of potential. I'm just not sure the marketing is there with the "help us win" motivation.

[ Parent | on HN ]
Re:Crowdsourcing Bruteforcing: Help me win the EngineYard ch... by mbrubeck on Monday July 20, 2009 @04:32PM (#715125)
This JavaScript version: http://news.ycombinator.com/item?id=715014 (which doesn't do any throttling) is doing ~1500 hashes per second in one Chrome tab on my fairly old (2.8 GHz Pentium D) desktop. I'm curious how fast it would be on your Core 2 Duo in two Chrome tabs.
[ Parent | on HN ]
Re:Crowdsourcing Bruteforcing: Help me win the EngineYard ch... by redorb on Monday July 20, 2009 @04:45PM (#715154)
Im getting about 3100/sec, on my duo centrino2 / thinkpad
[ Parent | on HN ]
Re:Crowdsourcing Bruteforcing: Help me win the EngineYard ch... by ErrantX on Monday July 20, 2009 @05:11PM (#715213)
Mine peaked at 3,450 or so on a Core2 Quad @ 3.2Ghz
[ Parent | on HN ]
Re:Crowdsourcing Bruteforcing: Help me win the EngineYard ch... by Retric on Monday July 20, 2009 @11:49PM (#715694)
I think GPU's are going to win this "Yeah, my 5 GPUs are currently cranking at a total rate of 800 M/sec" they are are already looking at the low 30's.
[ Parent | on HN ]
Re:Crowdsourcing Bruteforcing: Help me win the EngineYard ch... by jmtulloss on Monday July 20, 2009 @04:44PM (#715152)
Maybe a Google Native Client approach would have better luck. You would have to require your users be running Chrome, but it would be damn fast.
[ Parent | on HN ]