Measuring the page generation of the forum

[Somedude]

Le 13/04/2012 03:40, Vladimir Panteleev a écrit :
> On Thursday, 12 April 2012 at 18:36:01 UTC, SomeDude wrote:
>> Hi,
>>
>> I've noticed a couple of times (i.e very rarely, mind you), that the
>> page generation of the forum had hiccups.
>> Have other people experienced such hiccups ?
>> If yes, I wonder if we saw the GC kicking in, or if it was SQLite's
>> fault (or was it a network latency ?).
> 
> Long page loads are caused by a combination of high server load + RAM
> cache misses + SQLite queries that require a lot of seeks. I still
> haven't found the time for the migration to a more powerful server.
> 

Well, it's not really urgent. It's fast enough.
Still, collecting statistics over time would have been nice, so that one
could analyse the general behaviour of the GC, for instance, by getting
an idea of the standard deviation and maximum response time over weeks
of use. I guess since it can handle much larger loads, the forum server
is not stressed enough to give very meaningful insight under heavy load.
But I have experienced a response of several seconds once, I don't know
where this comes from (although it's most likely one of your reasons).
So collecting real time data would have to be done for each component of
the chain (SQLite, cache, D generated page). Such data would be useful
for any web server anyway.

BTW, could you repost the source code address ? Thx.

>> Is the server regularly restarted or is it running smoothly without
>> having to be restarted at all ?
> 
> It seems to run fine for weeks on end.

Nice.

> 
>> Does it measure the time for the page generation ? Would it be
>> interesting to see at the bottom of the page something like "Page
>> generated in xxx ms", when I (or other people) come accross those
>> hiccups, and to collect these data for statistics over a week/month ?
> 
> There are some numbers in the reddit discussion:
> 
> http://www.reddit.com/r/programming/comments/ppre5/the_new_d_online_forum_software_written_in_d/c3rfwte
> 

Nice, now I remember having read this post.