On mer, 2002-02-13 at 17:24, Jimmy Wales wrote:
Brion Vibber wrote:
I'm not sure what advantage would be gotten
out of storing a version
that has had HTML tags worked over, but still needs the wiki code
converted into HTML every time we load it. We get more speed by caching
the completely parsed version, or more storage savings by reparsing it
every time and not storing anything but the the editable text.
It's worth noting that on the live server, I see no material difference when
I turn caching on or off.
Interesting. I have to wonder whether this means caching is for some
reason not working at all... It seems to be disabled and/or broken at
the moment, unless someone sneaked in and fixed the other-languages bug
while I wasn't looking.
I ran "ab -n 10" on a couple pages running on my test server with
various states: caching on, caching off w/ no removeHTMLtags() call,
caching off with the old removeHTMLtags() code, and caching off with my
new as-yet unoptimized but more secure version of removeHTMLtags(). The
pages per second figures from three trials each:
Beryllium (large HTML table, various other tags)
* cached 2.06 2.06 2.16
* none 0.94 0.95 0.95
* old 0.90 0.90 0.89
* new 0.47 0.48 0.48
Esperanto-wiki mainpage: (a few <b>, <i>, and <font> tags)
* cached 3.26 3.13 3.47
* none 1.84 1.83 1.76
* old 1.82 1.80 1.80
* new 1.58 1.62 1.58
Also, space is really cheap these days. And we're
not in any immediate danger
of running out of it.
-- brion vibber (brion @ pobox.com