Fossil SCM
Further updates to the performance stats page: "yrs" becomes "years". Give a specific example of the commit bandwidth.
Commit
2762fecd9ef294b1abc2adbf60fc9f695cb5d33c
Parent
04eef9522386a59…
1 file changed
+11
-9
+11
-9
| --- www/stats.wiki | ||
| +++ www/stats.wiki | ||
| @@ -24,11 +24,11 @@ | ||
| 24 | 24 | |
| 25 | 25 | <tr align="center"> |
| 26 | 26 | <td>[http://www.sqlite.org/src/timeline | SQLite] |
| 27 | 27 | <td>56089 |
| 28 | 28 | <td>14357 |
| 29 | -<td>5388 days<br>14.75 yrs | |
| 29 | +<td>5388 days<br>14.75 years | |
| 30 | 30 | <td>3.4 GB |
| 31 | 31 | <td>45.5 MB |
| 32 | 32 | <td>73:1 |
| 33 | 33 | <td>29.9 MB |
| 34 | 34 | </tr> |
| @@ -35,11 +35,11 @@ | ||
| 35 | 35 | |
| 36 | 36 | <tr align="center"> |
| 37 | 37 | <td>[http://core.tcl.tk/tcl/timeline | TCL] |
| 38 | 38 | <td>139662 |
| 39 | 39 | <td>18125 |
| 40 | -<td>6183 days<br>16.93 yrs | |
| 40 | +<td>6183 days<br>16.93 years | |
| 41 | 41 | <td>6.6 GB |
| 42 | 42 | <td>192.6 MB |
| 43 | 43 | <td>34:1 |
| 44 | 44 | <td>117.1 MB |
| 45 | 45 | </tr> |
| @@ -46,11 +46,11 @@ | ||
| 46 | 46 | |
| 47 | 47 | <tr align="center"> |
| 48 | 48 | <td>[/timeline | Fossil] |
| 49 | 49 | <td>29937 |
| 50 | 50 | <td>8238 |
| 51 | -<td>2779 days<br>7.61 yrs | |
| 51 | +<td>2779 days<br>7.61 years | |
| 52 | 52 | <td>2.3 GB |
| 53 | 53 | <td>34.0 MB |
| 54 | 54 | <td>67:1 |
| 55 | 55 | <td>21.5 MB |
| 56 | 56 | </tr> |
| @@ -57,11 +57,11 @@ | ||
| 57 | 57 | |
| 58 | 58 | <tr align="center"> |
| 59 | 59 | <td>[http://www.sqlite.org/slt/timeline | SLT] |
| 60 | 60 | <td>2278 |
| 61 | 61 | <td>136 |
| 62 | -<td>2282 days<br>6.25 yrs | |
| 62 | +<td>2282 days<br>6.25 years | |
| 63 | 63 | <td>2.0 GB |
| 64 | 64 | <td>144.7 MB |
| 65 | 65 | <td>13:1 |
| 66 | 66 | <td>142.1 MB |
| 67 | 67 | </tr> |
| @@ -68,11 +68,11 @@ | ||
| 68 | 68 | |
| 69 | 69 | <tr align="center"> |
| 70 | 70 | <td>[http://www.sqlite.org/th3.html | TH3] |
| 71 | 71 | <td>8729 |
| 72 | 72 | <td>2406 |
| 73 | -<td>2347 days<br>6.43 yrs | |
| 73 | +<td>2347 days<br>6.43 years | |
| 74 | 74 | <td>386 MB |
| 75 | 75 | <td>15.2 MB |
| 76 | 76 | <td>25:1 |
| 77 | 77 | <td>12.6 MB |
| 78 | 78 | </tr> |
| @@ -79,11 +79,11 @@ | ||
| 79 | 79 | |
| 80 | 80 | <tr align="center"> |
| 81 | 81 | <td>[http://www.sqlite.org/docsrc/timeline | SQLite Docs] |
| 82 | 82 | <td>5503 |
| 83 | 83 | <td>1631 |
| 84 | -<td>2666 days<br>7.30 yrs | |
| 84 | +<td>2666 days<br>7.30 years | |
| 85 | 85 | <td>194 MB |
| 86 | 86 | <td>10.9 MB |
| 87 | 87 | <td>17:1 |
| 88 | 88 | <td>8.37 MB |
| 89 | 89 | </tr> |
| @@ -141,8 +141,10 @@ | ||
| 141 | 141 | The resulting CVS repository measured over 320MB in size. So, the |
| 142 | 142 | developers were surprised to see that the equivalent Fossil project (the |
| 143 | 143 | first nine years on SQLite) would clone with only 13MB of bandwidth. |
| 144 | 144 | The "sync" protocol |
| 145 | 145 | used by fossil has turned out to be surprisingly efficient. A typical |
| 146 | -check-in on SQLite might use 3 or 4KB of network bandwidth total, hardly | |
| 147 | -worth measuring. The sync protocol is efficient enough that, once cloned, | |
| 148 | -Fossil could easily be used over a dial-up connection. | |
| 146 | +check-in on SQLite might use 3 or 4KB of network bandwidth. | |
| 147 | +For example, the [04eef9522386a59e] check-in used a single HTTP request | |
| 148 | +of 2099 bytes and got back a reply of 1116 bytes. | |
| 149 | +The sync protocol is efficient enough that, once cloned, | |
| 150 | +Fossil can easily be used over a dial-up connection. | |
| 149 | 151 |
| --- www/stats.wiki | |
| +++ www/stats.wiki | |
| @@ -24,11 +24,11 @@ | |
| 24 | |
| 25 | <tr align="center"> |
| 26 | <td>[http://www.sqlite.org/src/timeline | SQLite] |
| 27 | <td>56089 |
| 28 | <td>14357 |
| 29 | <td>5388 days<br>14.75 yrs |
| 30 | <td>3.4 GB |
| 31 | <td>45.5 MB |
| 32 | <td>73:1 |
| 33 | <td>29.9 MB |
| 34 | </tr> |
| @@ -35,11 +35,11 @@ | |
| 35 | |
| 36 | <tr align="center"> |
| 37 | <td>[http://core.tcl.tk/tcl/timeline | TCL] |
| 38 | <td>139662 |
| 39 | <td>18125 |
| 40 | <td>6183 days<br>16.93 yrs |
| 41 | <td>6.6 GB |
| 42 | <td>192.6 MB |
| 43 | <td>34:1 |
| 44 | <td>117.1 MB |
| 45 | </tr> |
| @@ -46,11 +46,11 @@ | |
| 46 | |
| 47 | <tr align="center"> |
| 48 | <td>[/timeline | Fossil] |
| 49 | <td>29937 |
| 50 | <td>8238 |
| 51 | <td>2779 days<br>7.61 yrs |
| 52 | <td>2.3 GB |
| 53 | <td>34.0 MB |
| 54 | <td>67:1 |
| 55 | <td>21.5 MB |
| 56 | </tr> |
| @@ -57,11 +57,11 @@ | |
| 57 | |
| 58 | <tr align="center"> |
| 59 | <td>[http://www.sqlite.org/slt/timeline | SLT] |
| 60 | <td>2278 |
| 61 | <td>136 |
| 62 | <td>2282 days<br>6.25 yrs |
| 63 | <td>2.0 GB |
| 64 | <td>144.7 MB |
| 65 | <td>13:1 |
| 66 | <td>142.1 MB |
| 67 | </tr> |
| @@ -68,11 +68,11 @@ | |
| 68 | |
| 69 | <tr align="center"> |
| 70 | <td>[http://www.sqlite.org/th3.html | TH3] |
| 71 | <td>8729 |
| 72 | <td>2406 |
| 73 | <td>2347 days<br>6.43 yrs |
| 74 | <td>386 MB |
| 75 | <td>15.2 MB |
| 76 | <td>25:1 |
| 77 | <td>12.6 MB |
| 78 | </tr> |
| @@ -79,11 +79,11 @@ | |
| 79 | |
| 80 | <tr align="center"> |
| 81 | <td>[http://www.sqlite.org/docsrc/timeline | SQLite Docs] |
| 82 | <td>5503 |
| 83 | <td>1631 |
| 84 | <td>2666 days<br>7.30 yrs |
| 85 | <td>194 MB |
| 86 | <td>10.9 MB |
| 87 | <td>17:1 |
| 88 | <td>8.37 MB |
| 89 | </tr> |
| @@ -141,8 +141,10 @@ | |
| 141 | The resulting CVS repository measured over 320MB in size. So, the |
| 142 | developers were surprised to see that the equivalent Fossil project (the |
| 143 | first nine years on SQLite) would clone with only 13MB of bandwidth. |
| 144 | The "sync" protocol |
| 145 | used by fossil has turned out to be surprisingly efficient. A typical |
| 146 | check-in on SQLite might use 3 or 4KB of network bandwidth total, hardly |
| 147 | worth measuring. The sync protocol is efficient enough that, once cloned, |
| 148 | Fossil could easily be used over a dial-up connection. |
| 149 |
| --- www/stats.wiki | |
| +++ www/stats.wiki | |
| @@ -24,11 +24,11 @@ | |
| 24 | |
| 25 | <tr align="center"> |
| 26 | <td>[http://www.sqlite.org/src/timeline | SQLite] |
| 27 | <td>56089 |
| 28 | <td>14357 |
| 29 | <td>5388 days<br>14.75 years |
| 30 | <td>3.4 GB |
| 31 | <td>45.5 MB |
| 32 | <td>73:1 |
| 33 | <td>29.9 MB |
| 34 | </tr> |
| @@ -35,11 +35,11 @@ | |
| 35 | |
| 36 | <tr align="center"> |
| 37 | <td>[http://core.tcl.tk/tcl/timeline | TCL] |
| 38 | <td>139662 |
| 39 | <td>18125 |
| 40 | <td>6183 days<br>16.93 years |
| 41 | <td>6.6 GB |
| 42 | <td>192.6 MB |
| 43 | <td>34:1 |
| 44 | <td>117.1 MB |
| 45 | </tr> |
| @@ -46,11 +46,11 @@ | |
| 46 | |
| 47 | <tr align="center"> |
| 48 | <td>[/timeline | Fossil] |
| 49 | <td>29937 |
| 50 | <td>8238 |
| 51 | <td>2779 days<br>7.61 years |
| 52 | <td>2.3 GB |
| 53 | <td>34.0 MB |
| 54 | <td>67:1 |
| 55 | <td>21.5 MB |
| 56 | </tr> |
| @@ -57,11 +57,11 @@ | |
| 57 | |
| 58 | <tr align="center"> |
| 59 | <td>[http://www.sqlite.org/slt/timeline | SLT] |
| 60 | <td>2278 |
| 61 | <td>136 |
| 62 | <td>2282 days<br>6.25 years |
| 63 | <td>2.0 GB |
| 64 | <td>144.7 MB |
| 65 | <td>13:1 |
| 66 | <td>142.1 MB |
| 67 | </tr> |
| @@ -68,11 +68,11 @@ | |
| 68 | |
| 69 | <tr align="center"> |
| 70 | <td>[http://www.sqlite.org/th3.html | TH3] |
| 71 | <td>8729 |
| 72 | <td>2406 |
| 73 | <td>2347 days<br>6.43 years |
| 74 | <td>386 MB |
| 75 | <td>15.2 MB |
| 76 | <td>25:1 |
| 77 | <td>12.6 MB |
| 78 | </tr> |
| @@ -79,11 +79,11 @@ | |
| 79 | |
| 80 | <tr align="center"> |
| 81 | <td>[http://www.sqlite.org/docsrc/timeline | SQLite Docs] |
| 82 | <td>5503 |
| 83 | <td>1631 |
| 84 | <td>2666 days<br>7.30 years |
| 85 | <td>194 MB |
| 86 | <td>10.9 MB |
| 87 | <td>17:1 |
| 88 | <td>8.37 MB |
| 89 | </tr> |
| @@ -141,8 +141,10 @@ | |
| 141 | The resulting CVS repository measured over 320MB in size. So, the |
| 142 | developers were surprised to see that the equivalent Fossil project (the |
| 143 | first nine years on SQLite) would clone with only 13MB of bandwidth. |
| 144 | The "sync" protocol |
| 145 | used by fossil has turned out to be surprisingly efficient. A typical |
| 146 | check-in on SQLite might use 3 or 4KB of network bandwidth. |
| 147 | For example, the [04eef9522386a59e] check-in used a single HTTP request |
| 148 | of 2099 bytes and got back a reply of 1116 bytes. |
| 149 | The sync protocol is efficient enough that, once cloned, |
| 150 | Fossil can easily be used over a dial-up connection. |
| 151 |