{"id":794,"date":"2011-11-25T10:34:24","date_gmt":"2011-11-25T18:34:24","guid":{"rendered":"https:\/\/blogs.plm.automation.siemens.com\/t5\/Polarion-Blog\/Subversion-1-7-Zippy-but-should-you-upgrade\/ba-p\/380690"},"modified":"2026-03-26T05:30:54","modified_gmt":"2026-03-26T09:30:54","slug":"subversion-1-7-zippy-but-should-you-upgrade","status":"publish","type":"post","link":"https:\/\/blogs.sw.siemens.com\/polarion\/subversion-1-7-zippy-but-should-you-upgrade\/","title":{"rendered":"Subversion 1.7: Zippy, but should you upgrade?"},"content":{"rendered":"

by Lutz Dornbusch, Senior Consultant, Polarion Professional Services<\/EM><\/p>\n

\"RacecarSubversion 1.7<\/STRONG> is a release mostly devoid of new features, but with many performance improvements<\/STRONG>. From some users\u2019 highly appreciated WC-NG to mostly invisible HTTPv2, the question is what to expect from these improvements.<\/p>\n

Because Polarion\u2019s application lifecycle management products are built on top of Subversion, making SVN a core issue for our customers, we felt the need to highlight and benchmark some of the most visible performance boosts of SVN 1.7. I conducted tests with several key SVN operations and found some results impressive enough to suggest that upgrading to SVN is probably worthwhile for most users. But there are some important caveats as well, especially on the client side (at the time of this writing).<\/p>\n

In this article, I’ll share the results of my performance evaluation<\/STRONG> of Subversion 1.7 and recommendations for upgrading<\/STRONG>. If you like, you can download a PDF of this article<\/A><\/STRONG> (open download, no registration).<\/p>\n

Before you start reading – some handy links I’d like to share with you:
\n