22 ms·
That's really interesting. Are you able to tell us how long those 500k cores were running for before the facebookcorewwwi.onion name was found?
by wicket 10y ago
That's really interesting. Are you able to tell us how long those 500k cores were running for before the facebookcorewwwi.onion name was found?
- nocarrier 10y agoWe generated many candidates beginning with facebook, so I don't recall when that one was found--it just happened to be the one that looked the best. There's a number of backup memorable domains that we kept the keypairs for just in case facebookcorewwwi gets compromised somehow. I don't remember how long we ran it for, but IIRC we had enough candidates to stop after a week or two. I'm guessing something like 100-200M cpu hours?
- wicket 10y agoThanks for sharing! I'm now curious to know what the energy bill came to and whether it would make it to the list of most expensive domain names[1]. [1] https://en.wikipedia.org/wiki/List_of_most_expensive_domain_names https://en.wikipedia.org/wiki/List_of_most_expensive_domain_...
- danbruc 10y ago100M...200M core h, 10 W/core, 50 $/MWh and we get 50k...100k $.
- noir_lord 10y agoIt's awesome we live in a world where we can throw 100-200 million cpu hours at something of a whim. That each of those cores are billions of times faster than my first PC just puts the icing on the cake.
- evgen 10y agoFWIW, we ran it on and off for about a month IIRC, as the cluster was put through its paces prior to going live. I also seem to remember Matt Jones doing a minor tweak to the scallion code to speed things up as well...