I've published multiple benchmarks comparing different PostgreSQL versions, as for example the performance archaeology talk (evaluating PostgreSQL 7.4 up to 9.4), and all those benchmark assumed fixed environment (hardware, kernel, ...). Which is fine in many cases (e.g. when evaluating performance impact of a patch), but on production those things do change over time - you get hardware upgrades and from time to time you get an update with a new kernel version.
For hardware upgrades (better storage, more RAM, faster CPUs, ...), the impact is usually fairly easy to predict, and moreover people generally realize they need to assess the impact by analyzing the bottlenecks on production and perhaps even testing the new hardware first.
But for what about kernel updates? Sadly we usually don't do much benchmarking in this area. The assumption is mostly that new kernels are better than older ones (faster, more efficient, scale to more CPU cores). But is it really true? And how big is the difference? For example what if you upgrade a kernel from 3.0 to 4.7 - will that affect the performance, and if yes, will the performance improve or not?
Did you know - 2ndQuadrant has the largest single, collection of PostgreSQL experts of any company globally?!
With a team of some of the best known developers, they all still actively contribute to the progressive development of PostgreSQL. Would you like to have access to some of the most knowledgeable and experienced people available? The 5432...MeetUs! post-conference training is your chance!
In addition to the Kanban System Design training course with Dragos Dumitriu we mentioned last week, there will be a variety of other training courses in the days following the 5432...MeetUs! conference. When you attend a course with 2ndQuadrant, you learn from experts who understand PostgreSQL, the platforms, programs, and languages at the deepest level.
Learn in depth about the (more…)
Keynote speakers are always something everyone looks forward to at conferences. We're particularly looking forward to seeing Dragos Dumitriu team up with our very own Gabriele Bartolini at the 5432...MeetUs! conference in Milan, Italy June 28 and 29.
Dragos Dumitriu is an industry leader in the Agile community and renowned Kanban expert - helping to improve organisational efficiency in teams since 2004. 2ndQuadrant Italia has had a great friendship with Dragos since 2013 and will host him as a keynote speaker at the second edition of the 5432...MeetUs! conference. Dragos and Gabriele will discuss lean and Kanban in human enterprise environments, using 2ndQuadrant Italia as a live case study.
In addition to his talk, Dragos will host a certified Kanban training in the days after (more…)
The profiling utility perf that ships with the Linux kernel is extremely useful for examining system-wide and multi-process behaviour - but it does a lot more than the CPU profiling it's often used for. You've probably looked at perf top -az or perf top -u postgres output, but that's only the littlest bit of what it can do. (If you want the TL/DR version, jump down to "User space dynamic probes").
One of the big advantages of perf is that it's non-intrusive. You don't have to attach a debugger and interrupt execution. You don't have to run commands directly under a profiler in a special environment. There's no need to re-start the server to debug a problematic workload, and often no need to re-compile with debug options. This is extremely useful when you're trying to track down (more…)
My top #1 open source tool that I have discovered in the last year is definitely Vagrant. Vagrant is a software that helps you build and configure virtual environments for development and testing purposes. Vagrant relies on virtual machine providers such as VirtualBox, VMWare and AWS, as well as provisioning tools such as Chef and Puppet, allowing developers to clearly define their boxes using text files (which then can be easily versioned).
One of the key aspects of Barman is the possibility to remotely backup multiple PostgreSQL servers from one single backup host. The upcoming version 1.1.2 of Barman will make this much easier from a system administrator's point of view. Let's see why.
If you have a Linux server of the RedHat family (inclusing CentOS and Fedora), you might envy the way Debian/Ubuntu distributions handle PostgreSQL clusters management.
Although it is not easy to install different PostgreSQL versions on the same RedHat Linux server using RPMs, it is much simpler to install several instances of PostgreSQL (servers) and, at the same time, take advantage of the services infrastructure.