Talk:Current events/06/02

News ordering
Wouldn't it be easier to read if the latest news were at the top? -- Tihocan 07:05, February 15, 2006 (PST)


 * Not really. Links are supposed to anchor. Don't know why they aren't. 08:09, February 15, 2006 (PST)


 * Ah ok, that's the anchors mising that confused me -- Tihocan 09:05, February 15, 2006 (PST)

Hosting problems
Would there be a way to decrease the resource requirements of the Wiki by disabling some functionalities? I'm thinking for instance about counting accesses to all pages and showing it on each page. I have no idea if this would make any actual difference though. Tihocan 15:03, February 19, 2006 (PST)
 * Well, that would decrease it a tiny bit - much of the problem is that EVERYTHING you see is pulled from the database. Just for instance, try looking at the top-left hand corner of the page. Starting with the tabs, there are 10 queries (for me as an admin) - it pulls the word 'article' from the content of this wikipage: MediaWiki:article (I believe), it pulls the discussion tab from MediaWiki:Discussion and so on, then there are tons of other words on the page. This is to allow interface customization by the administrators and other such things, and to make it easier for us in general to fix things without fiddling with the source - for instance, I recently changed the text of MediaWiki:edit to 'edit this page' to clear up the fact that anybody can edit any page and to encourage other users to edit and correct things. Make sense? There are over 50 database queries per page - luckily, we have optimized MediaWiki enough that it actually loads pretty fast, and with some powerful customizations to our new server (woot!) we have mediawiki pages loading as fast as the browser can grab the HTML. The only problem that the script is so powerful and complicated with so many options and optimizations for end-user loading speed and usability, that each and every page load is very taxing on the server, simply in processing power. Bandwidth is not really a problem at all, luckily, everything is CSS instead of fugly images, so we only used about 0.3% of our alloted bandwidth in our time at dreamhost, and the new server's colocation has unmetered bandwidth anyway. Ending now. 15:13, February 19, 2006 (PST)
 * Ok, thanks for the explanation, so it's actually a server processing issue. Don't really know what to do except clicking on ads then :] -- Tihocan 07:27, February 20, 2006 (PST)