Many hyperlinks are disabled.
Use anonymous login to enable hyperlinks.
|Comment:||Update secondary mention of SQLite compression ratio to match table|
|Downloads:||Tarball | ZIP archive | SQL archive|
|Timelines:||family | ancestors | descendants | both | trunk|
|Files:||files | file ages | folders|
|User & Date:||andygoth 2018-06-09 16:37:44|
|10:36||Fix to the IfModifiedSince cache processing. check-in: 33fb3a97 user: drh tags: trunk|
|16:37||Update secondary mention of SQLite compression ratio to match table check-in: b46141f4 user: andygoth tags: trunk|
|09:41||Upgrade dirent to latest version (1.23.2, May 8, 2018) check-in: 1eee6c70 user: jan.nijtmans tags: trunk|
Changes to www/stats.wiki.
127 127 128 128 <h2>Analysis And Supplemental Data</h2> 129 129 130 130 Perhaps the two most interesting datapoints in the above table are SQLite 131 131 and SLT. SQLite is a long-running project with long revision chains. 132 132 Some of the files in SQLite have been edited over a thousand times. 133 133 Each of these edits is stored as a delta, and hence the SQLite project 134 -gets excellent 73:1 compression. SLT, on the other hand, consists of 134 +gets excellent 80:1 compression. SLT, on the other hand, consists of 135 135 many large (megabyte-sized) SQL scripts that have one or maybe two 136 136 edits each. There is very little delta compression occurring and so the 137 137 overall repository compression ratio is much lower. Note also that 138 138 quite a bit more bandwidth is required to clone SLT than SQLite. 139 139 140 140 For the first nine years of its development, SQLite was versioned by CVS. 141 141 The resulting CVS repository measured over 320MB in size. So, the