On: Creating a search engine with PostgreSQL

[vlovich123]

250k RPS seems like a lot when SQLite can’t do that today and I feel like inverted indices are more expensive (eg RocksDB gets to ~130k RPS but I think their numbers are on beefier hardware than my laptop or my machine isn’t set up well). Are you sure you wrote a general purpose database and those numbers are correct? I’m curious what you did to outperform these engines (I agree it’s possible, but I’m curious what techniques you employed)

[lionkor → vlovich123]

I'd guess:

- everything was in RAM,

- it was written in a compiled language, and

- probably skipped worrying about too many crazy edge cases

[thumbuddy → lionkor]

Same guesses I'd also add, single client without network connections. Anyone who says "writing a database from scratch is easy" makes me sweat profusely.

[hot_gril → thumbuddy]

Especially not easy if you actually implement read/write transactions (=> concurrency control, WAL, ...)