|Issue tags:||needs backport to D7|
I do not know how many sites out there use core's statistics module, but there are certainly some that do. There are a lot of 3rd party services that do the same thing (probably even better), but I've met webmasters that prefer integrated statistics, since it fits better into their workflow.
Statistics module is, from the other hand, not very flexible and not really performance friendly. There is no way to change or extend it's behaviour at all. It can also become a performance issue on high-traffic websites since it performs a DB write on every page request (webkenny have spoken about that topic in his session @ DrupalCon Chicago).
Simple performance optimisation could be done via cache. Statistics module could track visits in Drupal's cache and keep it there until first cron, when data will be written to DB. This wouldn't offer any benefit for default DB cache, but it will be much better when memcached or APC are used, which are, frankly, used on most high-traffic Drupal sites. This is currently, unfortunately, impossible to do without patching core.
Another possibility would be to move this module more towards a simple framework for statistics, that would log statistics via custom "engines". Each engine would be responsible for all "dirty work" behind the scenes. Core would in that case implement just default implementation, that can be similar than current one. Other engines could be implemented by contrib modules. This implementation could be similar to core's cache, where we have default DB cache in core and contrib modules that implement other cache backends.
Are there any plans in this direction? Are there any other ideas about this module?