“MB” == Michael Bielicki Michael.Blk@freezone.co.uk writes:
MB> BTW, to all postgresql users on the list:
MB> use postgresql 7.2
MB> bump up ur shared memory to at least 512MB
Depends on how much RAM you have. If you’re swapping your SHM
segments, it makes little sense – just let postgres fetch the data
from the disk itself.
If you can, tell your OS to make the SHM segments hard-wired physical
pages to eliminate the virtual memory overhead (FreeBSD can do this).
MB> run vaccum analyze full every 15 - 20 minutes (sic!)
No need for “full” vacuum anymore. RT never deletes rows, so you
don’t need to compact your tables to recover space from the deleted
rows. Any spaces left by updated rows will be reused after a plain
Once your DB is big enough, you don’t even need to run analyze more
than once per day or so. The statistics are just used by the query
planner to decide how to use indexes.
MB> and you will see an extreme speed increase
MB> btw … fastcgi is faster on my site than modperl by a factor of 3 …
Maybe because you’re sucking all of your RAM for your database… or
you’re running too many apps lumped into your apache. I have a
dedicated instance of apache for RT and it is incredibly fast, even
running under SSL.
With FastCGI, you just isolate the memory usage for RT to those
processes anyway, so the effect is the same as a seperate mod_perl-apache