5 reasons to upgrade to Subversion 1.7
The Apache Software Foundation announced the release of Subversion 1.7 , but which of the new features of 1.7 are useful to the user? And why not upgrade to version 1.7? Under the cut are five reasons for switching to Subversion 1.7.
In Subversion 1.7, the metadata copying system was completely rewritten. For the user, this means an immediate increase in performance. All the metadata for the working copy is now stored in the same repository in the root, so Subversion will no longer have to go through the entire directory tree to collect all the necessary information about the working copy.
At 1.7, the Subversion team decided to abandon DeltaV in favor of the new HTTP protocol "HTTPv2". This has several advantages for the user:
In version 1.6, an in-memory caching system was introduced, but many users experienced problems with an increase in the amount of allocated memory for the cache. Subversion 1.7 gives you more control over the cache:
Users who have a fairly good channel may lose more time to compress and decompress data than to transfer compressed data. Subversion 1.7 allows the user to adjust the level of data compression, which allows sending uncompressed data to the server and ultimately increasing the exchange rate with the server.
Subversion 1.7 gives users the ability to copy a dump to remote repositories. Admin access to storage is not required!
1) Fully rewritten working system of copying metadata
In Subversion 1.7, the metadata copying system was completely rewritten. For the user, this means an immediate increase in performance. All the metadata for the working copy is now stored in the same repository in the root, so Subversion will no longer have to go through the entire directory tree to collect all the necessary information about the working copy.
2) Improved HTTP protocol
At 1.7, the Subversion team decided to abandon DeltaV in favor of the new HTTP protocol "HTTPv2". This has several advantages for the user:
- Reduce DeltaV overhead (for example, an additional port in Apache for logging)
- Reducing client-server processing cycles for each request improves performance.
- Reduced server load (due to fewer requests to logs and reduced access to repositories.)
3) Taking control of the cache
In version 1.6, an in-memory caching system was introduced, but many users experienced problems with an increase in the amount of allocated memory for the cache. Subversion 1.7 gives you more control over the cache:
- Managing the memory used by the cache to prevent the large amounts of memory used by the cache.
- New caching structure and new code that has better performance in terms of memory usage.
4) Customizable compression ratio
Users who have a fairly good channel may lose more time to compress and decompress data than to transfer compressed data. Subversion 1.7 allows the user to adjust the level of data compression, which allows sending uncompressed data to the server and ultimately increasing the exchange rate with the server.
5) New remote dump feature 'svnrdump'
Subversion 1.7 gives users the ability to copy a dump to remote repositories. Admin access to storage is not required!
')
Source: https://habr.com/ru/post/130623/
All Articles