[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Wiki slowness

From: Thomas Schwinge
Subject: Re: Wiki slowness
Date: Mon, 31 Mar 2008 18:38:37 +0200
User-agent: Mutt/1.5.11


On Mon, Mar 17, 2008 at 09:53:09AM +0100, Arne Babenhauserheide wrote:
> El Saturday, 15 de March de 2008 15:11:21 Carl Fredrik Hammar escribiĆ³:
> > Ikiwiki seems to recompile markdown to html after every change.  If it
> > unnecessarily recompiles the *entire* wiki after each edit

It only compiles pages that have (a) been changed, (b) whose linkage
status has been changed (the ``Links:'' information at each page's
bottom) and (c) some cases I forgot.

> > or if git
> > is very io intensive, the slowness might be related to the problems in
> > diskfs.  But still, it seems to excessive to be caused by this alone.

The Hurd wiki is distributed over two Hurd system.  Please allow for some
delays in processing...  ;-)

Also, the web server is -- given today's standards -- a rather low-end
system.  Barry is working on getting some newer hardware in place.

If you need more speed, then use offline editing and ``git push &'' from
time to time.

> I just found out, that the committed stuff is avaible well before the edit 
> page says, that the site was changed. 
> Steps to reproduce: 
> * Open a wiki page (window 1). 
> * Edit it in a seperate window (window 2). 
> * Save the edited text in the seperate window (window 2). 
> * Reload the page in the original window from time to time (window 1). 
> The changes will be shown in the wiki (window 1) after a few minutes, but the 
> edit window (window 2) will still be loading for quite some time after that. 

This is because the edit frame only ``returnes'' until all ikiwiki stuff
has been done.  Which includes, e.g., updating the Recent Changes page,
which needs some time.  But at that time the edited page indeed has been
rendered already, so it is already available for browsing at that time.


Attachment: signature.asc
Description: Digital signature

reply via email to

[Prev in Thread] Current Thread [Next in Thread]