6 ms·
Out of interest (SQL Server guy mainly, so only partly keep up with what other engines are doing), what changes significantly affect performance (without making
by dspillett 8y ago
Out of interest (SQL Server guy mainly, so only partly keep up with what other engines are doing), what changes significantly affect performance (without making changes to your own code/configuration to make use of new features) in 10.x & 11.x?
- greggyb 8y agoBig parallelism updates that the query planner can take advantage of. I believe also updates to index seek or scan in that time.
- fabian2k 8y agoThere is usually a bunch of small improvements in every release, and those can add up over time. In Postgres 10 and 11 a lot of stuff happened related to parallel queries, and many more queries can be run in parallel now. 11 added a JIT compiler to the query planner, but I'm not sure whether that is enabled by default yet.
- cldellow 8y agoThe query planner in 10 got a lot better at enforcing row-level security constraints efficiently for some common scenarios, like 10-20x speedups. See https://github.com/postgres/postgres/commit/215b43cdc8d6b4a1700886a39df1ee735cb0274d https://github.com/postgres/postgres/commit/215b43cdc8d6b4a1... and the linked mailing list thread for more info, if you're curious.
- Scarbutt 8y agoOut of interest ;) SQL Server is such an expensive beast, ~$15K per core, what are your reasons for prefering it over PG?
- sovnade 8y agoIt's about $7000 per core for enterprise - and if you do something like license a whole blade and put VMs on top of it, you could fairly easily run 10-20+ SQL VMs on one decent sized blade for < 150k. And anything pre-prod is free. It's a small cost for most larger size companies of this scale. If you have one or two servers, then no, enterprise is probably out of reach.
- eropple 8y agoI quite like Postgres and use it preferentially, but your numbers are off. SQL Server Enterprise costs more like $7500/core; that $15K pack, as far as I am aware, comes with two core licenses. SQL Server Standard 2016 costs $931 for a license if you use CALs ($209 a pop), or $3700/core. Also bear in mind that almost nobody pays list price for any of this.
- Keyframe 8y ago$7500 per core, but only $15,000 for two cores sounds like a sweet deal though.
- grouseway 8y agoThere are no more server CPUs with less than 6 cores though. We could happily manage with just 2 dedicated to SQL server, but you have to license all the cores you have. So 3K worth of low end hardware ends up costing you several multiples of that in licensing.
- AlphaSite 8y agoI imagine a VM is a good solution to that.
- dspillett 8y ago> but you have to license all the cores you have Is that the case? I'm sure I've seen people running on limited cores for licencing reasons rather than having to licence every core. Not sir if that was enforced by the engine refusing to use more, or via seeing processor affinities.
- dspillett 8y agoDay job. Never had to pay for it out of my own pocket! I've worked at MS shops for quite some time. Also while we can do what we like with our newer SaaS offerings, getting some of our on-prem clients to use PG over SQL Server would be an uphill struggle so not considering other options isn't entirely our decision. That $15K sounds like an Enterprise Edition costing too, IIRC Standard is significantly cheaper. Most don't need Enterprise, especially since 2016Sp1 when a lot of previously Enterprise-only features became available in all editions (including the free Express edition in many cases). Developer edition is currently free (licensed for development use only, of course) and is essentially Enterprise edition with different licensing terms.
- mr_overalls 8y agoI use MS-SQL for my day job, and Postgres for personal projects. Pros of MS-SQL are mainly 1) easy integration with the universe of Microsoft dev tools, frameworks, and infrastructure, and 2) great database tooling in itself: * SSMS - SQL Server Management Studio * The MS BI stack: SSRS (reporting), SSAS (analysis), SSIS (integration)
- wongarsu 8y agoThe tooling is indeed sweet, and in a big company I could see it paying for itself in saved dev time.
- h1d 8y agoSounds like a victim of vendor lock in. I assume you will bleed hard to get out of it.
- mr_overalls 8y agoHow is this any different from the sunk cost that's a consequence of going with _any_ particular technology stack? I mean, if you chose Python/Postgres/etc., presumably, you'd have to rewrite/retool everything if you went to a different stack. If you're talking about open vs closed source: the C# compiler (Roslyn) is completely free and open source, as are a number of .NET components: CoreFX - Core foundational libraries, CoreCLR - runtime. As well as PowerShell, VS Code, Typescript, ASP.NET Core, MVC, Blazor, F#, Z3 Theorem Prover, etc. And that's from just the first few pages of their Open Source page: https://opensource.microsoft.com/ https://opensource.microsoft.com/
- polskibus 8y agoAnalysis Services, Integration Services, Clustered Index
- ape4 8y agoIt kinda bugs me that people say "SQL Server" to mean "Microsoft SQL Server". I mean, there are other sql servers.
- giovannibonetti 8y agoGood to know! Can you give an example? When I google "SQL Server" it seems like most results are related to MS SQL Server
- BubRoss 8y agoAn example of other SQL servers? PostgreSQL would be one, which is what this thread is about.
- dragonwriter 8y ago> It kinda bugs me that people say "SQL Server" to mean "Microsoft SQL Server". I mean there are other sql servers. I don't mind that; sure, there are other RDBMS servers that support SQL as their main or exclusive language, but unless you are talking about ancient Sybase products (for which there is a very good reason for the shared branding) “SQL Server” is a clear, exclusive Microsoft product identity and not any worse of a label, say, FTP (yes, there are other file transfer protocols). OTOH,what does bug me is when people say “SQL” to mean “Microsoft SQL Server”.
- buster 8y agohttps://en.wikipedia.org/wiki/SQL_Server https://en.wikipedia.org/wiki/SQL_Server Same as "FTP Server" doesn't mean proftpd, "HTTP Server" doesn't mean apache and "C compiler" doesn't mean gcc. SQL is a language. Server is a generic term. Another example: I may ask my colleague the following: "Which SQL server should we use in our new project?". Does this mean, i would like to know the edition and version of the MS SQL Server or maybe (and from my point of view more likely) i am looking for PostgreSQL, MySQL or MSSQL. If i'd like to know which edition and version i should use, i'd ask "Which MS SQL Server should i use?". That's a difference. Might be that our views differ but i can understand the parents points.
- SEJeff 8y agoOne of the huge ones was the ability to use > 1 cpu core for big aggregations or huge select queries. That and a massively better query planner.