Doing 60 million queries per second on a partitioned database isn't going to be ... | Hacker News

Hacker News new | past | comments | ask | show | jobs | submit

login

wmf 4 months ago | parent | context | favorite | on: Rearchitecting Core Services at X

Doing 60 million queries per second on a partitioned database isn't going to be easy either, and when you have problems you'll have to dig into the code of a database you didn't develop.

Demiurge 4 months ago [–]

Yeah, is there a PostgreSQL deployment that does 60m qps?

jiggawatts 4 months ago | [–]

Does Twitter actually need 60 qps, or is this just a consequence of not having JOIN operators?

Consider applying for YC's Spring batch! Applications are open till Feb 11.
Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact