I'm passionate about my job and I document all of my CockroachDB shenanigans. You can find them in my profile.
Motivation
The previous article left a lot to be desired and I've been meaning to get back to it. Today, we're going to improve on the original article by demonstrating what can be done to improve the performance of pgbench with CockroachDB. Typically, when customers begin their CockroachDB journey, they are faced with a learning curve having no prior knowledge of CockroachDB and many times, the biggest hurdle is isolation. CockroachDB operates in SERIALIZABLE isolation by default, full stop! There are no plans to change the status quo. Instead of weakening isolation, we advise our customers to practice defensible programming and change their application to work around the errors and retries. We're going to treat pgbench like a legacy application and demonstrate the problems and how we can work around them and modernize them for CockroachDB.