Database problems, anyone know PHP/MySql? (Help Merc!)
Posted September 21st, 2008 by jcaligori
Ok, I have built my Drigg installation into a pretty successful site over the last 3 months (see designbump.com). Page rank of 5, 600 members, lots and lots of scoops, etc.
My problem: Performance is not that great. I have drupal's caching activated. I am on a shared server with MediaTemple but am using almost no resources. It comes down to database load times and I know nothing about this. I have don't use many add on modules and I have used Devel to try and analyze the problem. I believe it comes from drigg having to sort through so many scoops. I don't have direct access to add any caching to the database (unless I upgrade my service but even then I wouldn't have the first idea about what to do).
Some info that I was told isn't ideal:
Select_full_join 522116
Select_range_check 2198
Handler_read_rnd 1,198 M
Handler_read_rnd_next 30 M
Etc.
Anyone have any suggestions on what the problem might be or how to fix this?
Extra incentive: If anyone can help me get this completely taking care of I will foot the rest of the tab for the EVB bounty (an extra 200 bucks).
Thanks!
John
Ugh...
Hi,
Database optimisation might be the only answer.
Drupal in general makes a zillion little queries. Unfortunately, Drigg doesn't help here either.
So... I am not sure. I am having similar problems at www.freesoftwaremagazine.com myself (!) but that's a server running two rather big sites, one based on Drigg and one based on "normal" Drupal.
I have this in my my.cnf conf file:
query_cache_size=32M
query_cache_type=1
query_cache_limit=3M
But it's obviously not working :-/
Merc.
Dang
Dang. Looks like I might be stuck for the time being then. Like I said, I don't even have access to the my.cnf file without upgrading my service. And I know nothing about database optimization.
I will give it some time, I suppose if the site keeps growing at this rate and it continues to slow I will have to find a paid service that can take care of this.
Thanks for taking the time to answer.
Best,
John