Should I turn off statistics tracking on client site?1 user found helpful
I read about the issue and how to disable stats onhttp://defunctlife.com/2009/08/how-to-disable-concrete5-site-statis... and I was concerned about it creating large database tables and slowing things down unnecessarily.
I don't want to break anything else though. I disabled it on my local system and everything seems to be fine but if you have more detail, I'd appreciate it.
I frantically found every reference to PageStatistics and commented it out of the code. Once the site was back up, I repaired the table and realized it had over 1.6 MILLION records.
I do like the stats built in to C5, but it seems like there might be a better method - increment a single record, rather than add a record every time someone visits the site...or something.
I know this is not a common issue for most people, but I just wanted to throw this out there.
So...andrew, franz? Any insight? Do you guys have this issue? Is your PageStatistics table huge?
You shouldn't have a lot of issues on performance outside of that graph on the dashboard home. That's the first thing to disable cause it does a horrible job summing things up quickly. You can leave the writes on as there aren't a lot of reads elsewhere in the system, but yeah by the time the table is 1.6 million rows you might want to flush it. ;)
I'll have Andy weigh in here too, but that's my perspective - we never sat down and architected the stats to be a solution for huge problems.
Ideally, we'd have some process that would allow statistics summarization so that the entire page statistics table didn't have to be queried, resulting in that slow graph. We just haven't done that yet.
There is one caveat, though: in 5.4.1, we're introducing full page caching. With our lazy db loading, if a page is cached entirely, when it loads it won't even initiate a connection to the database, making it even faster. This will ONLY happen, however, when you disable page statistics, because otherwise every page load needs to have a db connection. Fortunately, in 5.4.1 we've added a dashboard option to disable page statistics, making it easier to do. This is probably the way to go for high traffic sites using a third party stats engine.
Is the full page caching fully functional in 5.4.1b2?