PostgreSQL Scalability: Towards Millions TPS
akorotkov.github.io
PostgreSQL Scalability: Towards Millions TPS
1–10 of 222 posts
Re: PostgreSQL Scalability: Towards Millions TPS
#2Re: PostgreSQL Scalability: Towards Millions TPS
#3I don't know much but to me it seems PostgreSQL is probably one of the most open and supporting communities maybe this is reason alot of new faces are looking at it including me.
Re: PostgreSQL Scalability: Towards Millions TPS
#4Re: PostgreSQL Scalability: Towards Millions TPS
#5Re: PostgreSQL Scalability: Towards Millions TPS
#6Re: PostgreSQL Scalability: Towards Millions TPS
#7Re: PostgreSQL Scalability: Towards Millions TPS
#8Re: PostgreSQL Scalability: Towards Millions TPS
#9I had never touched PostgreSQL before, nor any Linux performance tools, but I noticed that replacing certain buffer eviction locks with atomic implementations could drastically help this particular case. I emailed the list about it and Andres was someone who chimed in with helpful advice. I wrote up what I'd discovered in my deep dive here: http://tiny.cc/postgres-concurrency
Turns out Andres was already working on a "better atomics" patch to provide easier methods of using atomic operations within PostgreSQL's code base (my patch was a quick hack probably only valid on x86, if that). It's been useful in removing several performance bottlenecks and—two years in—it looks like it's still paying off.
Re: PostgreSQL Scalability: Towards Millions TPS
#10The more efficient we can be at completing TPS reports the better. I must spend upwards of 40% of my time on them.