06-13-2009, 09:08 AM
Hi akhi Lars,
I'd look at the W3C http logs, and see what's causing the most CPU and taking the most resources.
In my case, (I also host a bible translation), 25% would be caused by web robots, looking for new / updated content, which is a waste of performance.
(I do not program perl, but perl.net could do this <!-- s
--><img src="{SMILIES_PATH}/smile.gif" alt="" title="Smile" /><!-- s --> the code is C#
<!-- m --><a class="postlink" href="http://edn.embarcadero.com/article/38123">http://edn.embarcadero.com/article/38123</a><!-- m -->
In my solution, each page, and chapter, the 'bible engine' calculates a ETAG using each primary key + timestamp per verse (because verses can be updated). So, a whole chapter or verse selection, can be precalculated an ETAG, and you will see performance improvements.
I'd look at the W3C http logs, and see what's causing the most CPU and taking the most resources.
In my case, (I also host a bible translation), 25% would be caused by web robots, looking for new / updated content, which is a waste of performance.
(I do not program perl, but perl.net could do this <!-- s
--><img src="{SMILIES_PATH}/smile.gif" alt="" title="Smile" /><!-- s --> the code is C#<!-- m --><a class="postlink" href="http://edn.embarcadero.com/article/38123">http://edn.embarcadero.com/article/38123</a><!-- m -->
In my solution, each page, and chapter, the 'bible engine' calculates a ETAG using each primary key + timestamp per verse (because verses can be updated). So, a whole chapter or verse selection, can be precalculated an ETAG, and you will see performance improvements.