[Due to server hardware (Hard disk) ?] DB Table crash due to hit counting

Thanks for the advice - ggppdk.

Sorry - where do I find unique counting?

We have done the following:
1. Our isotope universal module was generating many queries when it was set to extract images from Field. So - we have made it to extract from content by manually running the query to extract those images from the field - as we already know the file ID from where we got the image. I applied it to our sister site but not our other store site. The attached diagram shows the difference in memory and queries usage.


Image Link

2. We manually updated to innoDB as well.

I will repost in a few days to let you know how it goes.

Thanks,

Robert

Hello

innoDB might be a little slower in some cases, but is best choice, because it is almost crash proof and it's better locking does it more appropriate for update operations

do not forget to post an update

Hi ggppdk,

It crashed again - according to the server company:

"The caching service on the Cloud was stalled. It appears that the memory on the server was exceeded for a short time and this resulted in the stop of the MySQL and caching services"

We have 3gb of RAM - so I'm looking through my slow mysql logs and these keep appearing - but I don't really understand it:

1.
2.
3.
Any ideas?

Hello

these are normal

query 1 is backend and is cached 1 per login session , and happens in backend dashboard
-- (so it will not have any effect since it happens rarely)


query 3 is universal module and is using specific FLEXIContent item ID, using the same query with it, e.g. a Joomla module would be multiple times slower
- to call it slow please give some real numbers (milliseconds)


query 2 is also using ids
- same as above give some real numbers (milliseconds)

if they are the slowest queries, then they should be quite fast as they are quering specific IDs

Hello

you could use a solution that offers same/better perfromance without sharing the software processes

unfortunately siteground is using virtualization method that is sharing mysql Database process with other users
try using a software that requires full ACCESS to the DB like the popular Toad for MySQL, e.g. to do a DB comparison and siteground will tell you that you cannot have proper access, and you cannot change some MySQL configuration either !

e.g. this website has 120,000-150,000 page views per month (including bots) with 5%-15% (average 5 mins) CPU load during day
(OVH) 2x3GHz CPUs, with less RAM 2 GBs


also if you try to replace FLEXIcontent universal module with other module that needs similar query functionality you will find them to be much slower
also using a DB table smaller that ppp_content to make queries faster ... ppp_flexicontent_items_tmp

finally you can enable conservative/progressive caching in frontend, in v3 it should work properly in all cases

Hello

also if you do not enable cache Joomla will do more hits updates than FC, (same query), because FC by default will only count the page view once per user visit