I would be interested to see if you could get something like this running using the Google NACL project (http://code.google.com/p/nativeclient/). Wouldn't that give you then benefit of having native code running on any machine that went to the page and had the plugin installed? You could have the user install a plugin when they went to the page and then reload the page. Just popped into my head, probably too late to implement anything now, but might be fun to give it a go.
Crowdsourcing Bruteforcing: Help me win the EngineYard challenge
41–50 of 77 posts
Re: Crowdsourcing Bruteforcing: Help me win the EngineYard challenge
#42Re: Crowdsourcing Bruteforcing: Help me win the EngineYard challenge
#43As a CPU contributor, I demand that you give us stats as to which browsers were the fastest for your computation! This could be an interesting comparison point for the bundled javascript engines. (Maybe :))
Re: Crowdsourcing Bruteforcing: Help me win the EngineYard challenge
#44Also, are you logging IP's for your best results? Would be cool to know if my machine was the one that came up with the shortest hamming distance (obviously IP's aren't a guaranteed way to figure this out, but still...)
Re: Crowdsourcing Bruteforcing: Help me win the EngineYard challenge
#45This idea is a really well thought and implemented. This may be a new way of cloud sourcing. Have you considered making a facebook app? It would definitely attract many more people than this. Of course you shou ld offer some carrots for users that do not have any idea what's going on.
It's pretty well though out and is awesome in principle. The problem is that our interpreted javascript cloud network is getting owned by the awesome power of nVidia GPUs.
"Yeah, my 5 GPUs are currently cranking at a total rate of 800 M/sec. (Best score of 39 after running for a few minutes.)
(Hah! Just got lucky and hit 35 on one card after an hour.) " - The nVidia CUDA group
Re: Crowdsourcing Bruteforcing: Help me win the EngineYard challenge
#46Earlier quoted context omitted.
Also decrease rate at which HTML stats are updated - DOM update slows stuff down, it should update stats only once a second or so.
Updated to 1ms! I'll work on the HTML stat updates Edit: fixed and fixed
Now we're talking! 7 tabs = 80% cpu usage!
You might also consider lookup tables for Hamming distance (google for "counting bits").
Re: Crowdsourcing Bruteforcing: Help me win the EngineYard challenge
#47Earlier quoted context omitted.
Also decrease rate at which HTML stats are updated - DOM update slows stuff down, it should update stats only once a second or so.
Updated to 1ms! I'll work on the HTML stat updates Edit: fixed and fixed
Yeah, my JS hamming distance implementation is pretty miserable. I'm no bit wizard, but I thikn I can modify the SHA1 function (before it returns the value as a hex string) and XOR the 5 vars with the hex value that they gave us, and then count the set bits. Couldn't get it working last night though so I switched over to this
Re: Crowdsourcing Bruteforcing: Help me win the EngineYard challenge
#48Earlier quoted context omitted.
Also decrease rate at which HTML stats are updated - DOM update slows stuff down, it should update stats only once a second or so.
Updated to 1ms! I'll work on the HTML stat updates Edit: fixed and fixed
You might also consider removing UTF8Encoding from SHA1 implementation, I might be wrong, but I think contest states no encoding should be used - i.e. ASCII only. If that's a care, that's a useless O(N) operation.
Re: Crowdsourcing Bruteforcing: Help me win the EngineYard challenge
#49Earlier quoted context omitted.
Also decrease rate at which HTML stats are updated - DOM update slows stuff down, it should update stats only once a second or so.
Updated to 1ms! I'll work on the HTML stat updates Edit: fixed and fixed
Hah! I just generated as many hashes in a minute that I did in the hour I had it running beforehand. Good changes :)
Re: Crowdsourcing Bruteforcing: Help me win the EngineYard challenge
#50To get more people excited, might be a good idea to say how many cycles each browser has contributed - make it a fight of Chrome vs Firefox vs Safari ;)