Continuing on from my previous posts, MySQL code size over releases and MariaDB code size I’ve decided to also look into some other code branches. I’ve used the same methodology as my previous few posts: sloccount for C and C++ code only.
There are also other branches around in pretty widespread use (if only within a single company). I grabbed the Google, Facebook and Twitter patches and examined them too, along with Percona Server 5.1 and 5.5.
|Codebase||LoC (C, C++)||+/- from MySQL|
|Google v4 patch 5.0.37||970,110||+26,378 (from MySQL 5.0.37)|
|MySQL@Facebook||1,087,715||+15,768 (from MySQL 5.1.52)|
|Percona Server 5.1 trunk||1,066,418||+14,878 (from MySQL 5.1.66)|
|Percona Server 5.5 trunk||1,208,577||+19,483 (from MySQL 5.5.29)||+142,159 (from PS 5.1)|
The Google patch has always had a reputation of being large, and with an extra 26kLOC of code, it certainly is the biggest of any of the more current branches – and that’s actually a surprise to me that it adds this much code.
The Facebook and Percona Server 5.1 branches are amazingly similar in how much extra code they add, and they’re not carbon copies of each other. The Twitter patch quite notable for how little extra code it adds.
For giggles, I included Drizzle – which is (even with all the plugins) less than a third of the size of MySQL 5.1.
It’s clear that the Percona Server and Facebook patches introduce much less code than MariaDB does, which does go with the general wisdom of them being closer to Oracle MySQL than MariaDB is.
If we look at Percona Server, we see that with Percona Server 5.5 there is indeed a bunch more code than was in Percona Server 5.1, with roughly 5,000 more lines of code than we’d expect from a simple port from MySQL 5.1 to MySQL 5.5. This feels about right, we’ve added new things to Percona Server 5.5 that weren’t in Percona Server 5.1.