Ever added an index, confirmed with EXPLAIN that Postgres is actually using it and the query was still slow?
The index isn't the problem. Selectivity is.
The fix usually isn't a better index. It's a more selective query.
I wrote up the full debugging path: what to look for in EXPLAIN (ANALYZE, BUFFERS), and what to do when the answer is "nothing will help here".
https://t.co/xNTk9TyNsS
@strzibnyj@CamposLVictor Why do you think it is not production ready? Although I agree with mentioned limitations but the provided functionality is production ready which you can extend.
Takes 12 modern cores to do 50K requests per second? How about 58K cores (over 15% more) on my 3 year old 8 core laptop (33% less cores)?
How'd I get it so much faster? Easy, I used Ruby!
I used 8 threads for wrk instead of 12 coz my 8 cores, had I had 12, it would do better
Takes 12 modern cores to do 50K requests per second? How about 58K cores (over 15% more) on my 3 year old 8 core laptop (33% less cores)?
How'd I get it so much faster? Easy, I used Ruby!
I used 8 threads for wrk instead of 12 coz my 8 cores, had I had 12, it would do better
If more developers ran Linux on their desktop, maybe they wouldn't be so petrified of running a server by themselves. We are unlearning the basics of the Internet at an alarming rate.
🎁Give Away 100 System Design Books🎁
🔹 10 signed physical books (vol1+vol2 +ML, winners get all 3)
🔹 90 1-year ByteByteGo online course
How to participate:
✅ Follow
✅ Like & RT
✅ Subscribe free newsletter: https://t.co/ssb0DDW1rR
⏰ Giveaway ends in 72 hours