From: LS <alp...@ya...> - 2002-10-02 05:29:12
|
Hi- Can anyone suggest why PHPWiki is so slow, or how I can configure it to make it faster? I just installed phpwiki-1.3.3 from CVS on my RH7.3 Linux server running Apache/2.0.40 (Unix) PHP/4.3.0-dev and MySQL4.0a. I host a number of small PHP sites and they all respond very quickly, despite the server being a P166 with 92MB RAM, but for some reason PHPWiki takes about 1.4 seconds to render typical pages. RecentChanges takes nearly 7 seconds. I am trying to get folks at my office to embrace the Wiki world, but they are complaining about the site being too slow. The pages take the same amount of time to load via lynx on localhost. I do not have PHPA running on the server, as it does not yet support Apache2, and I'm wondering if there is just a hell of a lot of PHP parsing that has to happen each time the Wiki is called. Or perhaps there is just a lot of database updates that need to happen and PEAR isn't handling them well. If anyone has suggestions on how to use PHPWiki on a small server, please let me know. Thanks! __________________________________________________ Do you Yahoo!? New DSL Internet Access from SBC & Yahoo! http://sbc.yahoo.com |
From: Reini U. <ru...@x-...> - 2002-10-02 09:55:27
|
LS schrieb: > Hi- > Can anyone suggest why PHPWiki is so slow, or how I can configure it to make it > faster? > > I just installed phpwiki-1.3.3 from CVS on my RH7.3 Linux server running > Apache/2.0.40 (Unix) PHP/4.3.0-dev and MySQL4.0a. I host a number of small PHP > sites and they all respond very quickly, despite the server being a P166 with 92MB > RAM, but for some reason PHPWiki takes about 1.4 seconds to render typical pages. > RecentChanges takes nearly 7 seconds. > I am trying to get folks at my office to embrace the Wiki world, but they are > complaining about the site being too slow. The pages take the same amount of time > to load via lynx on localhost. > I do not have PHPA running on the server, as it does not yet support Apache2, > and I'm wondering if there is just a hell of a lot of PHP parsing that has to > happen each time the Wiki is called. Or perhaps there is just a lot of database > updates that need to happen and PEAR isn't handling them well. > If anyone has suggestions on how to use PHPWiki on a small server, please let > me know. for me 1.3.4pre and 1.3.3 is of about the same speed. jeff's page cache and the upgrade to the new pear DB brought it to the same speed as of the previous ADODB in 1.3.2. tried the ZendOptimizer? is it innodb on mysql4? maybe it's also apache2. also 92MB RAM is very low. we typically have from 512MB to 1.5GB RAM on our servers. -- Reini Urban http://xarch.tu-graz.ac.at/home/rurban/ |
From: Joby W. <joby@u.washington.edu> - 2002-10-02 14:46:06
|
LS wrote: > I just installed phpwiki-1.3.3 from CVS on my RH7.3 Linux server running > Apache/2.0.40 (Unix) PHP/4.3.0-dev and MySQL4.0a. I host a number of small PHP > sites and they all respond very quickly, despite the server being a P166 with 92MB > RAM, but for some reason PHPWiki takes about 1.4 seconds to render typical pages. > RecentChanges takes nearly 7 seconds. I don't know if anyone has tested Apache 2.0/PHP 4.3 with phpwiki. But your server is most likely the issue. A P166 with 92MB is really lite to run phpwiki. Phpwiki is a pretty big app. Every page access requires the loading of many (10+) php files, and then the content of the page must be parsed as well. This is probably competing with your MySQL database to be in memory. Thus when the php parser is activated your MySQL database is getting dumped to swap. And when php makes MySQL calls, MySQL is brought back to memory and the php/apache process is dumped to swap. etc... This would indicate a need for a new server. Perhaps you can keep apache/php/phpwiki on your P166/92MB, but stick MySQL on another old computer -- though this introduces network latency... jbw |
From: <ph...@de...> - 2002-10-02 16:45:57
|
On Wed, 02 Oct 2002 07:45:57 -0700, Joby Walker wrote: => Phpwiki is a pretty big app. Every page access => requires the loading of many (10+) php files, and then the content of => the page must be parsed as well. Which is *really* unfortunate for those of us trying to make phpWiki work as an additional collaborative tool for clients hosted on shared servers (such as those at http://www.pair.com). I always keep my fingers crossed that our very creative phpwiki dev team keeps us in mind as they continue to improve this great "little" app. Cheers, - Don (who is looking forward to the next "release") |
From: Reini U. <ru...@x-...> - 2002-10-02 17:26:50
|
ph...@de... schrieb: > On Wed, 02 Oct 2002 07:45:57 -0700, Joby Walker wrote: > => Phpwiki is a pretty big app. Every page access > => requires the loading of many (10+) php files, and then the content of > => the page must be parsed as well. > > Which is *really* unfortunate for those of us trying to > make phpWiki work as an additional collaborative tool for clients > hosted on shared servers (such as those at http://www.pair.com). > > I always keep my fingers crossed that our very creative > phpwiki dev team keeps us in mind as they continue to improve > this great "little" app. Pretty big? I work with php apps which load > 500 php files per page request. Also on public serverhosts, with lots of load. But if it's too slow for you, we can think of optionally concatenating the generally required files alltogether to ease your pain. In some kind of Makefile. (untested. just to get the idea) Makefile: BACKEND = sql DB_ROOT = root DB_ROOTPASS = DB_USER = wikiuser DB_PASS = fixme WIKI_DB = phpwiki ALL = index.php lib/main.php lib/prepend.php ... noop : true install : install-mysql echo "read INSTALL" echo "browse to configurator.php" install-mysql : !if DB_ROOT mysqladmin -u$(DB_ROOT) -p$(DB_ROOTPASS) create $(WIKI_DB) mysql -u$(DB_ROOT) -p$(DB_ROOTPASS) -e"GRANT select, insert, update, delete ON $(WIKI_DB).* TO $(DB_USER)@localhost IDENTIFIED BY '$(DB_PASS)'" !endif mysql -u$(DB_USER) -p$(DB_PASS) $(WIKI_DB) < schemas/mysql.sql single-file : phpwiki.php phpwiki.php: $(ALL) cat $(ALL) > phpwiki.php # patch phpwiki.php to disable most require calls for $s in $ALL; do perl -pi.bak -e"s|require_once\('$s'\)|//$&|" phpwiki.php done echo "use phpwiki.php as your DirectoryIndex" and so on... I've done this single-file version for my autolisp standard library, with the help of a simple perl script. But I found no performance advantage, only administrative. Even on windows which has aching slow fileaccess. -- Reini Urban http://xarch.tu-graz.ac.at/home/rurban/ |