• Resolved Andrzej


    Is anyone else seeing a huge statcomm database size? I’m suspecting this is causing our website slowdown.

    I have tried disabling User Agent String Database and Maxmind and reducing Days in Overview graph to 30 – with no affect. Changing auto-delete visits and spiders from none -> 1 year also has no affect. In all cases, statcomm dbase remains at 39 MiB.

    Is there some way to tune the plugin to reduce dbase size?


Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Author WPReady


    Hi Andrzej,

    Changing the Overview graph will change how many days to draw, it
    wouldn’t affect the plugin performance.

    I recommend deactivate the plugin(s) and test the site speed before and after. Check the performance using P3 (Plugin Performance Profiler) http://wordpress.org/extend/plugins/p3-profiler/

    On Statcomm overview, below all the boxes, there is a ‘Time Summary’ box where you can see render time and table size, among other information. Typical times should be under 5 seconds.

    If you want to reduce the database size I would recommend change settings ‘Automatically delete visits older than’ to 3 months for example and ‘Automatically delete spiders older than’ to one month or suppress it completely using ‘Do not collect spiders visits’ checkbox.

    Disabling User Agent String Database will disable also the ability of Statcomm for detecting OS and browsers. This should be used in special cases when you are certain you have plugin problems not necessarily performance ones.

    Currently I’m testing the plugin with 500MB tables and there is no performance hit.

    Hope this help you!

    It appears that performance issues are more related to our hosting service. Other customers are also reporting slow site operations.

    At first I suspected wp3.5 and its interaction with plugins. Then I found the large Statcomm table – thanks for your reassurance and suggestions about this. Will apply your tuning suggestions when time allows.


Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘39 MiB dbase’ is closed to new replies.