News for hackers. Stuff that matters.
Re:Why Searching Through 500M Pwned Passwords Is So Quick by th3byrdm4n on Tuesday February 27, 2018 @11:52AM (#16475255)
Precisely my first thought. Static readonly data? Why isn't this just sitting in memory?
Re:Why Searching Through 500M Pwned Passwords Is So Quick by vortico on Tuesday February 27, 2018 @12:12PM (#16475478)
Don't filesystem caches basically do this for you?
Re:Why Searching Through 500M Pwned Passwords Is So Quick by zaroth on Tuesday February 27, 2018 @12:23PM (#16475618)
Yes but with a heck of a lot more overhead than;

  response.body = result[(int)hexCode];
Re:Why Searching Through 500M Pwned Passwords Is So Quick by tgsovlerkhgsel on Tuesday February 27, 2018 @08:00PM (#16479774)
No, with a lot less overhead because you don't need to write custom web server code.

Edit: and if he points the requests directly at blob storage as he's suggesting, we're very close to to flat files on a filesystem again.

Re:Why Searching Through 500M Pwned Passwords Is So Quick by dullgiulio on Tuesday February 27, 2018 @01:45PM (#16476525)
You can do that after mmap(2) and you never have to reach out for read(2). Might need to use unsafe language constructs though.
Re:Why Searching Through 500M Pwned Passwords Is So Quick by mzzter on Tuesday February 27, 2018 @12:11PM (#16475467)
Sounds reasonable, 500mil * 160 bits of SHA-1 would be 500 mb of space. Even with some metadata to manage it, the smallest instances should be able to handle that.
Re:Why Searching Through 500M Pwned Passwords Is So Quick by lipnitsk on Tuesday February 27, 2018 @12:22PM (#16475603)
500,000,000*160bits/(8bits/byte)=10,000,000,000 bytes=9,536MB=9.313GB