Quote:
Originally posted by CS-Jay
Yhea it's basically going every part of the server(s) and getting each part to work.
So far, hardware is in place. The db is optimized. Apache is lookin pretty good. It's about time to go over the code, but besides that I am running pretty good. I guess I am just trying to sqeeze s some more juice outta that beauch.
|
having hardware in place and getting the most out of it is a big difference ..
first (if you use IDE Hds) .. what is the result of hdparm -tT /dev/hda1 .. (or whatever you mount your hd to) .. ?
the database is the crucial part and I bet that your performance could be at least 500 % higher in optimizing it .. just a stupid example regarding locking issues on a busy system ... Wrong: Delete from table where tableID = xyz .. right: insert xyz into tableB... select * from table right outer join tableB on table.xyz = tableB.xyz ..
setting right indexes can improve performance significantly .. using wrong indexes will reduce it .. and I bet that your db structure is full with indexes that are not used at all and just slow your system down .. having the right multicolumn indexes is the key ..
ok, this post could be endless ..
http://dev.mysql.com has some VERY interesting articles .. but .. you need to read them very thourughly and be fluent in sql to understand them ..