Mark Christensen wrote:
1) A second hard drive for the main database server.
You will generally
see a significant performance improvement from having applications,
logs, and the OS on one drive, and only the DB on the other.
yes, this is a good idea. and it seems economic seeing as hdd are cheap
these days.
3) Move the remaining wiki's off of the DB server,
and shut down
everything you can (PHP, Apache, etc).
I thought this was the plan all along.. To slowly start switching all
the wiki's off the db server as they were all setup with the latest
software.
4) Memory and (to a lesser extent) CPU upgrades can
make a significant
impact on performance under the right conditions.
It seems at the moment memory is our pain problem, memory gets full and
the server starts swapping and thats just a horrible horrible viscious
cycle.
I don't know where the current bottlenecks are, but
if it is anywhere in
the DB, the above might help significantly.
I believe they are mostly in the DB. I'm trying to look through the code
and find some DB bottle necks, but I am having a pretty hard time
because I guess I'm not that familiar with the codebase and since its so
different from my normal programming style It takes longer for me to put
everything together.
All this talk of upgrading is great, but it all requires money. I am
personally ready to pitch in a bit, I can't afford much, but I would
like to throw in what I can. I wish I could donate more actual work, but
I'm having trouble with the codebase. Jimbo recently mentioned he is in
the process of opening a paypal and merchant account. Hows that process
going?
I think a flowchart of what exactly happens upon a call to the server
would be great. and it would include all function calls and all querys.
there we could see how many query's we are doing. and see what could be
edged out.
Lightning