Fossil SCM

Fix a busted hyperlink in the previous change to server.wiki.

drh 2014-03-10 00:22 trunk
Commit 60774eb33fa1556c443c8c271444cb00a79df15e
1 file changed +3 -3
+3 -3
--- www/server.wiki
+++ www/server.wiki
@@ -246,18 +246,18 @@
246246
<a name="loadmgmt"></a>
247247
<h2>Managing Server Load</h2><blockquote>
248248
<p>
249249
A Fossil server is very efficient and normally presents a very light
250250
load on the server.
251
-The Fossil [selfhost.wiki | self-host server] is a 1/24th slice VM at
251
+The Fossil [./selfhost.wiki | self-host server] is a 1/24th slice VM at
252252
[http://www.linode.com | Linode.com] hosting 65 other repositories in
253253
addition to Fossil (and including some very high-traffic sites such
254254
as [http://www.sqlite.org] and [http://system.data.sqlite.org]) and
255255
it has a typical load of 0.05 to 0.1. A single HTTP request to Fossil
256256
normally takes less than 10 milliseconds of CPU time to complete. So
257
-requests can be arriving at a continuous rate of 10 or 20 per second
258
-without significantly burdening the server.
257
+requests can be arriving at a continuous rate of 20 or more per second
258
+and the CPU can still be mostly idle.
259259
<p>
260260
However, there are some Fossil web pages that can consume large
261261
amounts of CPU time, expecially on repositories with a large number
262262
of files or with long revision histories. High CPU usage pages include
263263
[/help?cmd=/zip | /zip], [/help?cmd=/tarball | /tarball],
264264
--- www/server.wiki
+++ www/server.wiki
@@ -246,18 +246,18 @@
246 <a name="loadmgmt"></a>
247 <h2>Managing Server Load</h2><blockquote>
248 <p>
249 A Fossil server is very efficient and normally presents a very light
250 load on the server.
251 The Fossil [selfhost.wiki | self-host server] is a 1/24th slice VM at
252 [http://www.linode.com | Linode.com] hosting 65 other repositories in
253 addition to Fossil (and including some very high-traffic sites such
254 as [http://www.sqlite.org] and [http://system.data.sqlite.org]) and
255 it has a typical load of 0.05 to 0.1. A single HTTP request to Fossil
256 normally takes less than 10 milliseconds of CPU time to complete. So
257 requests can be arriving at a continuous rate of 10 or 20 per second
258 without significantly burdening the server.
259 <p>
260 However, there are some Fossil web pages that can consume large
261 amounts of CPU time, expecially on repositories with a large number
262 of files or with long revision histories. High CPU usage pages include
263 [/help?cmd=/zip | /zip], [/help?cmd=/tarball | /tarball],
264
--- www/server.wiki
+++ www/server.wiki
@@ -246,18 +246,18 @@
246 <a name="loadmgmt"></a>
247 <h2>Managing Server Load</h2><blockquote>
248 <p>
249 A Fossil server is very efficient and normally presents a very light
250 load on the server.
251 The Fossil [./selfhost.wiki | self-host server] is a 1/24th slice VM at
252 [http://www.linode.com | Linode.com] hosting 65 other repositories in
253 addition to Fossil (and including some very high-traffic sites such
254 as [http://www.sqlite.org] and [http://system.data.sqlite.org]) and
255 it has a typical load of 0.05 to 0.1. A single HTTP request to Fossil
256 normally takes less than 10 milliseconds of CPU time to complete. So
257 requests can be arriving at a continuous rate of 20 or more per second
258 and the CPU can still be mostly idle.
259 <p>
260 However, there are some Fossil web pages that can consume large
261 amounts of CPU time, expecially on repositories with a large number
262 of files or with long revision histories. High CPU usage pages include
263 [/help?cmd=/zip | /zip], [/help?cmd=/tarball | /tarball],
264

Keyboard Shortcuts

Open search /
Next entry (timeline) j
Previous entry (timeline) k
Open focused entry Enter
Show this help ?
Toggle theme Top nav button