another performance hint: if you have a lot of entries/wiki spaces you might want to consider taking a look at postgreSQL or mySQL as db- storage instead of SQLite, that comes with instiki. of course this should just speed up write-access, since most of the read-access is cached anyway.
see http://instiki.org/show/Instiki+and+MySQL http://instiki.org/show/Instiki+and+Postgresql -m On 01.11.2007, at 16:28, José Bonnet wrote: > Brutal! > Just upgrading from 0.11 to 0.12 gives me an acceptable speed! > jb > On Oct 31, 2007, at 8:22 PM, Matthias Tarasiewicz wrote: > >> jose, >> can you tell us on which system you are running instiki? are you >> using >> apache2 with mongel or webrick? >> >> for a good performing solution you might want to >> * switch to the latest instiki 0.12 version >> * run a load balancer (nginx with mongrel seems to be the fastest >> solution) >> >> see >> http://wiki.codemongers.com/NginxRubyonRailsMongrel >> http://brainspl.at/articles/2006/08/23/nginx-my-new-favorite-front- >> end-for-mongrel-cluster >> >> -matthias >> >> On 10/31/07, José Bonnet <[EMAIL PROTECTED]> wrote: >>> Hi! >>> I've been using the wonderful Instiki for two years now, but I'm >>> facing performance problems (rampant rendering times). >>> >>> Any help? >>> >>> jb >>> _______________________________________________ >>> Instiki-users mailing list >>> [email protected] >>> http://rubyforge.org/mailman/listinfo/instiki-users >>> >> _______________________________________________ >> Instiki-users mailing list >> [email protected] >> http://rubyforge.org/mailman/listinfo/instiki-users > > _______________________________________________ > Instiki-users mailing list > [email protected] > http://rubyforge.org/mailman/listinfo/instiki-users _______________________________________________ Instiki-users mailing list [email protected] http://rubyforge.org/mailman/listinfo/instiki-users
