Ability to disable statistics (create ad_statistics as separate module) [#1339208]

I would love it if ad_statistics became it's own module, so that we could turn off the excessive logging when it's not needed. None of the sites I use ad on actually need statistics tracking (since most of our ads come from ad services) but that ad_statisitcs table is always the largest table in my whole database. Seems such a waste!

Comments

Comment #1

Jeremy CreditAttribution: Jeremy commented 12 November 2011 at 18:37

Version:

6.x-3.x-dev

» 6.x-2.x-dev

It should be simple enough to just add a configuration option to globally disable all statistics for the module, as all statistics are tracked in a central function. We'd need to confirm this would work with the ad_cache_* modules as well (likely simplest they'd be collected by the cache, but thrown away instead of being inserted into the database).

Comment #2

Jeremy CreditAttribution: Jeremy commented 12 November 2011 at 18:40

I took a quick look -- unfortunately what I said is not entirely true. The caching layers can insert into the database directly -- so to support this feature it would take changes in multiple places. Still, quite doable.

Comment #3

jenlampton

she / her

CreditAttribution: jenlampton commented 10 February 2012 at 05:32

Until we get this ironed out, I've created a tiny statistics killer: http://drupal.org/sandbox/jenlampton/1435124

But let me know when there's a patch to test :)

Comment #4

andrewtf CreditAttribution: andrewtf commented 2 October 2012 at 20:00

Flushing the ad statistics on cron could be really useful. However it would be preferable to be able to export or backup the statistics in a meaningful way (as a csv file or spreadsheet, for example) in case advertisers want to know how their ad's been performing. It actually doesn't happen too often, but of course the last time I truncated a too-huge ad statistics table via PHPmyadmin someone came of the woodwork and asked for a clickthrough number…