*** dthacker_away is now known as dthacke1
*** Yann_ is now known as Yann2
<Yann2> http://master.ubuntu-eu.org/weblogs/overall/daily_usage_200610.png < edgy \o/ :)
<mitsuhiko> Yann2: jep :D
<Mirv> Yann2: just in theory, in case it seems it takes months for Canonical to really fix / get up to speed the LoCoTeam servers, how's the situation with ubuntu-eu's server (speed/space), and is it welcoming new LoCoTeams?
<Mirv> I'd really think Canonical will fix the problems, but people have been a bit annoyed for some time already because of the slowness problems, and I still don't know any ETAs or such
<Yann2> Mirv > we actually don't welcome new teams, as the cpu usage is growing _fast_
<Yann2> Mirv > but anyway, we'll never achieve to get an as good uptime as a company like canonical :)
*** jalrnc_ is now known as jalrnc
<Mirv> Yann2: yeah, I was just curious. good to know that also you have increasing amount of users :)
<Mirv> a common "problem" in the Ubuntu world...
<Yann2> I think our moinmoin is killing us, if we could optimize this we may have room for others again :)
<Mirv> big response times all in all are killing our server
<Mirv> requests go into a queue and then more lag occurs and more requests go into queue
<Mirv> there wouldn't probably be a problem if edgy was not just released... Canonical people have probably enough work anyway, and of course part of them are probably even resting...
<Mirv> but it's now again today a bit better than it was yesterday, so maybe we can handle a little more wait
<Yann2> :)
<Yann2> the whole games is to find the bottlenecks :)
<JanC> moinmoin is filesystem-based...
<Yann2> that doesn't mean it has to be so slow :)
<Yann2> dokuwiki is filesystem based too ;)
<Yann2> JanC , what wiki are you using?
<JanC> the main ubuntu wiki
<Yann2> that's moinmoin :)
<JanC> I know
<JanC> choosing another filesystem or tuning the existing one might help...
<JanC> it will probably also mean a higher data loss risk ;)
<Yann2> I think there are one or 2 functions from this wiki, that make it a lot slower, and that might not be needed
<JanC> what caching headers do you / does it use ?
<Yann2> ?
<JanC> telling browsers to cache pages for some (longer) time might help
<Yann2> yup
<JanC> it's just a bit annoying for editors maybe
<Yann2> may also cause consistency problems :)
<Yann2> yep
<JanC> an intelligent server-side cache might help too
<Yann2> oh.. we tried :/
<Yann2> it was such a pain
<Yann2> (squid)
<JanC> if moinmoin can be teached to invalidate pages that have been changed
<JanC> I mean something intelligent and using in-memory caching
<Yann2> i'm not a python expert... ubuntu-de is using moin, i don't :)
<JanC> does the server have enough RAM free?
<Yann2> >2GB cache
<Yann2> Mirv > you're ubuntu-fi right? i don't find it that slow :)
<Mirv> Yann2: it's better today.. during the last week it's often been so that there are 20-40s load times for a page
<Mirv> and yes, ubuntu-fi .)
<Yann2> :)
<Yann2> what teams are on this loco server?
<Mirv> well, I'm not sure.. but newz2000 has said that we are the ones that are really getting that server hammered, so I guess we are the largest one and the others are some smaller (IT-wise) countries
<Mirv> and there was this complete blackout when they had this great idea of moving also Ubuntu Italy to the same server -> total downtime of ca. 15 hours :)
<Yann2> \o/ :D
<Yann2> downtimes happen :)
<Yann2> 15 hours isn't even that bad ;)
<Yann2> imagine, hmm, your motherboard dies :D
<JanC> we don't really have load problems for Belgium, as all languages spoken here are "foreign" languages (as in: there is a large(r) community of speakers outside Belgium, and people use the respective forums etc.)
<Yann2> oh, JanC , are you the new -be locoteam leader?
<Yann2> s/leader/contact
<JanC> I'm the team contact, not the team leader :)
<Yann2> hey, congrats :)
<JanC> btw: if you have > 2 GiB RAM, it should be possible to just keep the whole wiki in RAM and still have plenty of free memory :P
<Yann2> and hoping it'll never reboot :)
<JanC> but I guess the problem is that pages get rendered every page view again
<Yann2> i don't know moinmoin
<Yann2> jalrnc is our new moinmoin expert :]
<JanC> no, I mean caching the rendered version of the last revision
<JanC> but I don't know moinmoin and if that's possible
<JanC> :)
<Yann2> i think there already is caching :)
<JanC> if you have (good) caching there shouldn't be a problem with something like a wiki IMHO
<JanC> it's not like all pages change every minute or so
<Yann2> page rendering is not necessarily the pages that cause the wiki to be slow
<JanC> if you have a forum that might be the culprit too
<Yann2> on dokuwiki, the heaviest pages were rss feed and last changes pages
<Yann2> nope the forums are ok
<JanC> rss feeds are sometimes hammered by idiots that check them every minute or so
<Yann2> in dokuwiki it just was poorly coded with a dumb utf8encode clone function
<Yann2> and that function in the rss feed caused the whole server to become damn slow :)
<JanC> on a site of a non-profit that I work for, we generate static rss feeds when articles get added to the site
<JanC> (added or removed or changed in fact)
*** yama` is now known as yama_away
*** yama_away is now known as yama
<Yann2> yup
<Yann2> but this whole performance tuning need involving in the core of the script we uses... and that needs a LOT of time :)
<JanC> hehe
*** yama is now known as yama_away
<MagicFab> Updated: https://wiki.ubuntu.com/EdgyReleaseParties

Generated by irclog2html.pl 2.1 by Jeff Waugh - find it at freshmeat.net!