MediaWiki 1.3.9 and 1.4beta4 are very slow and uses too many CPU cycles and memory compared to other wikis. The database schema, as I see it, seems to be inefficient. Are there any changes planned for 1.4 final to increase performance?
On Jan 15, 2005, at 2:54 PM, NSK wrote:
MediaWiki 1.3.9 and 1.4beta4 are very slow and uses too many CPU cycles and memory compared to other wikis. The database schema, as I see it, seems to be inefficient. Are there any changes planned for 1.4 final to increase performance?
The database schema is inefficient, but that has little to do with CPU cycles or memory. 1.5 makes major changes to the schema.
Major changes prior to 1.4 are not expected as we're long since in the final beta cycle; 1.4 is already twice as fast as 1.3 for many requests (see http://meta.wikipedia.org/wiki/MediaWiki_1.4_benchmarks) and enables the parser cache by default which reduces most page view times to the minimum.
Memory usage is primarily from PHP's overhead in loading the script files. CPU usage without a PHP opcode cache is primarily from PHP's overhead in compiling the script files. With a PHP opcode cache, CPU usage is divided among several things, and there is ongoing work to reduce this. Nonspecific "it's slow" comments do very little productive help in this regard.
If MediaWiki does not suit your needs compared to other wikis, please feel free to use other wikis instead. We aren't going to feel bad, and we didn't lose a sale.
-- brion vibber (brion @ pobox.com)
If MediaWiki does not suit your needs compared to other wikis, please feel free to use other wikis instead. We aren't going to feel bad, and we didn't lose a sale.
-- brion vibber (brion @ pobox.com)
I think it would be better to listen to any complains from any users. MediaWiki is not perfect by any means. The biggest improvements should come from the comparision with other wikis.
Again, you can only claim "I am not going to feel bad." not "We". Who were "We" here !?
I bet you attitude and words hurted many people and the whole project now and in a long run. We are going to lose! You are an important person currently for this project. The attitude of important persons really matter.
So be cautious to your attitude. Please.
I hate to critize people face to face. But I think somebody has to take that role in addition many others are praising you. Keep in mind that I am also very thankful for your diligent work for this project. :-)
Kiss All
did you try installing the PHP booster Turck MMCache? I'm not allowed to on my shared server - but it appears to give performance a big boost.
Paul ----- Original Message ----- From: "NSK" nsk2@wikinerds.org To: wikitech-l@Wikimedia.org Sent: Saturday, January 15, 2005 11:54 PM Subject: [Wikitech-l] performance
MediaWiki 1.3.9 and 1.4beta4 are very slow and uses too many CPU cycles and memory compared to other wikis. The database schema, as I see it, seems to be inefficient. Are there any changes planned for 1.4 final to increase performance?
-- NSK http://portal.wikinerds.org _______________________________________________ Wikitech-l mailing list Wikitech-l@wikimedia.org http://mail.wikipedia.org/mailman/listinfo/wikitech-l
It's also certainly worth looking at installing Squid (http://www.squid-cache.org) if you haven't, yet. That made a huge difference on the MW install I've got on an intranet at work, and also reduced the memory footprint.
cheers, -Nick
Paul Youlten wrote:
did you try installing the PHP booster Turck MMCache? I'm not allowed to on my shared server - but it appears to give performance a big boost.
Paul ----- Original Message ----- From: "NSK" nsk2@wikinerds.org To: wikitech-l@Wikimedia.org Sent: Saturday, January 15, 2005 11:54 PM Subject: [Wikitech-l] performance
MediaWiki 1.3.9 and 1.4beta4 are very slow and uses too many CPU cycles and memory compared to other wikis. The database schema, as I see it, seems to be inefficient. Are there any changes planned for 1.4 final to increase performance?
-- NSK http://portal.wikinerds.org _______________________________________________ Wikitech-l mailing list Wikitech-l@wikimedia.org http://mail.wikipedia.org/mailman/listinfo/wikitech-l
Wikitech-l mailing list Wikitech-l@wikimedia.org http://mail.wikipedia.org/mailman/listinfo/wikitech-l
Out of curiosity, has anyone experimented with configuring cacheing within apache itself?
http://httpd.apache.org/docs-2.0/mod/mod_cache.html
It is my understanding that squid takes advantage the same pragma headers that mod cache can look at - I wonder if there is an intermediate configuration that can be tuned and recommended without having to install a separate proxy server.
mod_cache is something I plan to look at in conjunction with MW as soon as performance requirements demands it (and time permits ).
/Jonah
----- Original Message ----- From: "Nick Triantos" nick@triantos.com To: "Wikimedia developers" wikitech-l@wikimedia.org Sent: Sunday, January 16, 2005 5:48 PM Subject: Re: [Wikitech-l] performance
It's also certainly worth looking at installing Squid (http://www.squid-cache.org) if you haven't, yet. That made a huge difference on the MW install I've got on an intranet at work, and also reduced the memory footprint.
cheers, -Nick
Paul Youlten wrote:
did you try installing the PHP booster Turck MMCache? I'm not allowed to on my shared server - but it appears to give performance a big boost.
Paul ----- Original Message ----- From: "NSK" nsk2@wikinerds.org To: wikitech-l@Wikimedia.org Sent: Saturday, January 15, 2005 11:54 PM Subject: [Wikitech-l] performance
MediaWiki 1.3.9 and 1.4beta4 are very slow and uses too many CPU cycles and memory compared to other wikis. The database schema, as I see it, seems to be inefficient. Are there any changes planned for 1.4 final to increase performance?
-- NSK http://portal.wikinerds.org _______________________________________________ Wikitech-l mailing list Wikitech-l@wikimedia.org http://mail.wikipedia.org/mailman/listinfo/wikitech-l
Wikitech-l mailing list Wikitech-l@wikimedia.org http://mail.wikipedia.org/mailman/listinfo/wikitech-l
Wikitech-l mailing list Wikitech-l@wikimedia.org http://mail.wikipedia.org/mailman/listinfo/wikitech-l
Just an FYI.. I only have ~130 users on my intranet MW install. I made an article that I thought would be useful, so I emailed it out to a wide audience, and ended up slashdotting my own wiki server. I didn't get that many hits, I don't think, but each one was trying to render that same page, and it ended up filling memory and the paging file. I installed Squid shortly after that.
The lesson: Don't wait for performance requirements to demand it. ;-)
-Nick
Jonah Bossewitch wrote:
Out of curiosity, has anyone experimented with configuring cacheing within apache itself?
http://httpd.apache.org/docs-2.0/mod/mod_cache.html
It is my understanding that squid takes advantage the same pragma headers that mod cache can look at - I wonder if there is an intermediate configuration that can be tuned and recommended without having to install a separate proxy server.
mod_cache is something I plan to look at in conjunction with MW as soon as performance requirements demands it (and time permits ).
/Jonah
----- Original Message ----- From: "Nick Triantos" nick@triantos.com To: "Wikimedia developers" wikitech-l@wikimedia.org Sent: Sunday, January 16, 2005 5:48 PM Subject: Re: [Wikitech-l] performance
It's also certainly worth looking at installing Squid (http://www.squid-cache.org) if you haven't, yet. That made a huge difference on the MW install I've got on an intranet at work, and also reduced the memory footprint.
cheers, -Nick
Paul Youlten wrote:
did you try installing the PHP booster Turck MMCache? I'm not allowed to on my shared server - but it appears to give performance a big boost.
Paul ----- Original Message ----- From: "NSK" nsk2@wikinerds.org To: wikitech-l@Wikimedia.org Sent: Saturday, January 15, 2005 11:54 PM Subject: [Wikitech-l] performance
MediaWiki 1.3.9 and 1.4beta4 are very slow and uses too many CPU cycles and memory compared to other wikis. The database schema, as I see it, seems to be inefficient. Are there any changes planned for 1.4 final to increase performance?
-- NSK http://portal.wikinerds.org _______________________________________________ Wikitech-l mailing list Wikitech-l@wikimedia.org http://mail.wikipedia.org/mailman/listinfo/wikitech-l
Wikitech-l mailing list Wikitech-l@wikimedia.org http://mail.wikipedia.org/mailman/listinfo/wikitech-l
Wikitech-l mailing list Wikitech-l@wikimedia.org http://mail.wikipedia.org/mailman/listinfo/wikitech-l
Wikitech-l mailing list Wikitech-l@wikimedia.org http://mail.wikipedia.org/mailman/listinfo/wikitech-l
Nick Triantos wrote:
Just an FYI.. I only have ~130 users on my intranet MW install. I made an article that I thought would be useful, so I emailed it out to a wide audience, and ended up slashdotting my own wiki server. I didn't get that many hits, I don't think, but each one was trying to render that same page, and it ended up filling memory and the paging file. I installed Squid shortly after that.
Squid is great for the slashdot effect. If all the requests are for a small set of pages (fitting in RAM), a single low-end server running squid can fill a 100 Mbps link. As long as your upstream network can handle that bandwidth, you can keep a very large flash crowd happy.
-- Tim Starling
Jonah Bossewitch wrote in gmane.science.linguistics.wikipedia.technical:
Out of curiosity, has anyone experimented with configuring cacheing within apache itself?
http://httpd.apache.org/docs-2.0/mod/mod_cache.html
It is my understanding that squid takes advantage the same pragma headers that mod cache can look at - I wonder if there is an intermediate configuration that can be tuned and recommended without having to install a separate proxy server.
Last time I looked at mod_proxy it did not understand the PURGE request type. MediaWiki needs this to tell the proxy to purge its cache. I don't know if this applies to mod_cache or if there's a different way to do it - I wasn't interested in caching at the time so I didn't look closely.
Kate.
wikitech-l@lists.wikimedia.org