[pmwiki-users] Pmwiki.org website performance

Patrick R. Michaud pmichaud at pobox.com
Wed Apr 12 10:41:18 CDT 2006


On Wed, Apr 12, 2006 at 07:53:32AM -0700, pmwiki at 911networks.com wrote:
> >>2. VPS and you have your own 512Mb? How many other servers on
> >>that box?
> >
> >I have my own 512Mb (bursting to 2Gb).  I don't know how many other
> >VPS's are on the box -- that's not normally information that a
> >webhosting service provides...
> 
> Depending on your  part of the world, a cable/DSL connection and 
> dedicated server would solve this problem while being much 
> cheaper. In Canada: cable/fixed IP, 3Mbps, 50 Gb/month is around 
> US$130.

Right now my VPS is $US 80/month (I just upgraded from $45/month), 
so it's not "cheaper".  

I already have cable/DSL, and while I regularly get around 6Mbps
downlink speed, the uplink speed is only about 384Mbps.  I could
perhaps upgrade my service to a fixed IP with a faster (768Mbps) 
uplink speed, but I'd still have to buy the dedicated server.

Also, I'm hosting several domains besides pmwiki.org within my VPS, 
so I'd still have to continue paying for VPS, or else get a cpanel
license of some sort to continue to support my other clients.

Still, it's a good idea, and if things get much worse for pmwiki.org
I may see about moving to a dedicated server.  The traffic on the
site continues to grow.  :-)

> Only 4000 pages, should all fit in RAM [it's all text] and disk 
> should not be a concern.

You're right -- it should all fit into RAM (the raw text files
total only 46MB).  But it's not the file contents that seem to 
cause delays -- it's the lag from performing open() and stat() 
calls on the files, and I'm not sure that information is held in 
RAM, especially if the disk is actually a virtual storage device.

> 1. How much memory has been allocated to PHP? Can you 
> increase/set it to 32M or 64M

PHP is running without memory limits -- see 
http://www.pmwiki.org/wiki?action=phpinfo .

> 2. Are you using eaccelerator? If not you should, it makes a 
> world of difference. My website [not PM yet] went from 10-15sec 
> to under 2sec and often under 1sec. I allocated 64Mb to eaccelerator.

I'll see about giving it a try.  The improvement in compile speed
wouldn't seem to be that big an issue; PmWiki isn't a large
program (<6500 lines even if every possible script is loaded),
and it already gets through the entire configuration section 
in less than a few hundredths of a second:

    00.00 00.00 config start
    00.00 00.00 config end
    00.00 00.00 stdconfig begin
    00.02 00.00 skin.php pmwiki begin
    00.02 00.00 skin.php pmwiki end
    00.03 00.01 stdconfig end
    00.05 00.03 MarkupToHTML begin

Still, I'm a little curious to see what sorts of optimizations 
eaccelerator might give, so I may try it when I get a chance.

Thanks!

Pm




More information about the pmwiki-users mailing list