Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

PostgreSQL Scalability: Towards Millions TPS

akorotkov.github.io

Post reply on HN
Print view View original

91–100 of 222 posts

Re: PostgreSQL Scalability: Towards Millions TPS

#91

Post by brisance »

combatentropy wrote: post #85
jrcii wrote: post #12

Slightly tangential but I'm genuinely curious, does any have a theory as to why nearly every RDBMS post on Hacker News is about Postgres and almost never MySQL or MariaDB? Considering the relative obscurity of the former it seems somewhat inexplicable.

> why nearly every RDBMS post on Hacker News is about Postgres and almost never MySQL You'll see the same phenomenon on Slashdot. MySQL is popular among a subset of programmers: web developers. In corporations, Microsoft SQL and Oracle are more popular. Further, MySQL is popular among a subset of web developers: those who use PHP. Among web developers who use Python, Postgres seems more popular. My suspicion is that…

>>The strangest thing to me is not that MySQL is more popular than Postgres, but that anyone uses Microsoft or Oracle at all. Not only do they cost a lot, but from a purely technical standpoint they are worse.

A lot of decisions are made holistically instead of a "purely technical standpoint". In large companies where there are still IT departments (e.g. use of Active Directory), MS is still very much the de facto platform, and SQL Server is the "logical" choice.

Re: PostgreSQL Scalability: Towards Millions TPS

#93

Post by m_mueller »

_w3e8 wrote: post #82

Postgres has been my DB of choice for nearly a decade. The only times I wind up working with another db are because: (1 it is a better technical fit for a very specific problem (2 there is already a legacy db in place I have been voted down at a couple of startups that wanted to run a "MEAN" stack, invariably all of those startups moved from MongoDB or shutdown. The only time I will advocate for anything other than P…

How would you handle replicating a DB to mobile devices? This is the reason why I've been using CouchDB, but if Postgres or a plugin offered something comparable I'd have gone for it for sure.

Re: PostgreSQL Scalability: Towards Millions TPS

#94

Post by ziedaniel1 »

anarazel wrote: post #86
AbacusAvenger wrote: post #77

Earlier quoted context omitted.

I wonder, does Intel's TSX/HLE help with these workloads? If it's read-only then I'd expect that it'd be able to elide a lot of the locking (assuming the Intel-designed heuristics do the job).

I'd bought one of the first haswell notebooks to play around with tsx. Before I'd time to do so Intel found the tsx bug... I hope to have time to play around with it one I have new hardware (I refuse to do performance development on virtual). But honestly, most remaining performance/scalability problems in pg are more algorithmically caused. So micro optimization, and that's what I'd call tax/hle, aren't likely to bi…

Wasn't TSX only enabled on Xeons to begin with?

Re: PostgreSQL Scalability: Towards Millions TPS

#95

Post by nisa »

the-dude wrote: post #53
jlgaddis wrote: post #36

Man, how I wish WordPress had originally chosen to use PostgreSQL instead of MySQL back in the day.

http://www.hawkix.net/pgsql-for-wordpress/ https://wordpress.org/plugins/postgresql-for-wordpress/

    Compatible up to: 3.4.2
    Last Updated: 2 years ago
    Active Installs: 400+
WordPress 4.5 is current. Anyone doing WordPress will just skip this if they don't have developers that can fix the issues. Also while the base may work a lot of popular plugins (used to?) don't utilize WP_Query or whatever else WordPress offers.

It's also probably easier to add indexes to the code or rewrite the logic. Mostly it's bad database code that sucks on MySQL and would likely suck the same way on PostgreSQL.

Besides that if you use an object cache like memcache or redis you can avoid a lot of database accesses and InnoDB seems to be able to deal with concurrent tables like wp_comment.

Would be cool to see in WordPress itself but I doubt it.

Re: PostgreSQL Scalability: Towards Millions TPS

#96

Post by charliedevolve »

__float wrote: post #88
_w3e8 wrote: post #82

Postgres has been my DB of choice for nearly a decade. The only times I wind up working with another db are because: (1 it is a better technical fit for a very specific problem (2 there is already a legacy db in place I have been voted down at a couple of startups that wanted to run a "MEAN" stack, invariably all of those startups moved from MongoDB or shutdown. The only time I will advocate for anything other than P…

What do you mean by MySQL avoiding an additional database dependency?

I think he meant that MySQL is the only supported DB for Wordpress, and while you might be able to get it running on another DB after jumping through some hoops, it's probably not worth the effort.

Re: PostgreSQL Scalability: Towards Millions TPS

#97

Post by virmundi »

m_mueller wrote: post #93
_w3e8 wrote: post #82

Postgres has been my DB of choice for nearly a decade. The only times I wind up working with another db are because: (1 it is a better technical fit for a very specific problem (2 there is already a legacy db in place I have been voted down at a couple of startups that wanted to run a "MEAN" stack, invariably all of those startups moved from MongoDB or shutdown. The only time I will advocate for anything other than P…

How would you handle replicating a DB to mobile devices? This is the reason why I've been using CouchDB, but if Postgres or a plugin offered something comparable I'd have gone for it for sure.

Out of curiosity, how often do your detached DBs update old records? The reason I ask is nostalgia. A company I worked with used MySQL as an embedded DB (laptops under their control). Yesterday, I thought about how absurd this was. The DB only inserted new records and read static records. An embedded SQL would have worked great here. Would that be true for you too?

Re: PostgreSQL Scalability: Towards Millions TPS

#99

Post by anarazel »

ziedaniel1 wrote: post #94
anarazel wrote: post #86

Earlier quoted context omitted.

I'd bought one of the first haswell notebooks to play around with tsx. Before I'd time to do so Intel found the tsx bug... I hope to have time to play around with it one I have new hardware (I refuse to do performance development on virtual). But honestly, most remaining performance/scalability problems in pg are more algorithmically caused. So micro optimization, and that's what I'd call tax/hle, aren't likely to bi…

Wasn't TSX only enabled on Xeons to begin with?

No, the higher end i7 mobile processors had it as well (i7 48xxhq or something IIRC).

Re: PostgreSQL Scalability: Towards Millions TPS

#100

Post by tomc1985 »

combatentropy wrote: post #85
jrcii wrote: post #12

Slightly tangential but I'm genuinely curious, does any have a theory as to why nearly every RDBMS post on Hacker News is about Postgres and almost never MySQL or MariaDB? Considering the relative obscurity of the former it seems somewhat inexplicable.

> why nearly every RDBMS post on Hacker News is about Postgres and almost never MySQL You'll see the same phenomenon on Slashdot. MySQL is popular among a subset of programmers: web developers. In corporations, Microsoft SQL and Oracle are more popular. Further, MySQL is popular among a subset of web developers: those who use PHP. Among web developers who use Python, Postgres seems more popular. My suspicion is that…

While I love me some PG, SQL Server is nothing to sneeze at. Was fairly impressed with it, never had any serious issues on an under-specced server once occupied by terrible programmers
Post reply on HN