Creating an advanced search engine with PostgreSQL

Re:Creating an advanced search engine with PostgreSQL by vlovich123 on Wednesday July 12, 2023 @08:30PM (#36703566)

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)

[ Parent | on HN ]

Re:Creating an advanced search engine with PostgreSQL by lionkor on Thursday July 13, 2023 @05:04AM (#36706583)

I'd guess:

- everything was in RAM,

- it was written in a compiled language, and

- probably skipped worrying about too many crazy edge cases

[ Parent | on HN ]

Re:Creating an advanced search engine with PostgreSQL by thumbuddy on Thursday July 13, 2023 @07:08AM (#36707417)

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.

[ Parent | on HN ]

Re:Creating an advanced search engine with PostgreSQL by hot_gril on Friday July 14, 2023 @12:46PM (#36726455)

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

[ Parent | on HN ]