1,145 karma · joined November 3, 2008
One odd thing is that the article used 2 python workers when using gunicorn but a single when using tornado. Seems a bit unfair to say the least :)
Go to http://www.peterbe.com/plog/mincss and click to view source. 120Kb of bootstrap excess baby!
I started it but it's been actively maintained by over 30 coders over several active years.
And it's pretty cool that you can make a choice between fast writes or safe writes. You can't have both but at least you can have the choice.
Having said all that, I generally prefer Postgres in almost every possible case.
However, this RethinkDB project looks sexy and with a great potential.
I investigated the problem and found a very good explanation for why it was happening.
Solved now: https://github.com/peterbe/autocompeter/commit/a31c919c1281d...
If this service becomes surprisingly popular I'll look into ways to monetize but that's unlikely to be the case unless I'm really really lucky.
The origin of building this is that I found a cool prototype of the concept in a blog post, then threw that into my own site and later realized I want to re-use that for a (day)work site. So I though instead of copying it, I'll write a microservice.
2. I see. I think it only happens when the client-side cache is empty. And it only happens if you type very fast. I think the right solution would be to not hide too quickly. That's a very useful piece of feedback. Much appreciated!
I actually re-wrote it once to switch out Redis for Postgres but it was way too slow.
However, the hit ratio is too low to work. It only protects me from the stampeding herd problem at best.