Database suggestion

  • Resolved teodorsavic

    (@teodorsavic)


    11 years, 8 months ago

    Hi, I’m using this plugin for a day now and I’m amazed how good it is. It gives so much information and it’s really great. I rated 5 stars.
    One suggestion though. I had 120.000 pageviews in less than 24 hours and my database is growing FAST. It’s almost 25MB now (in less than a day).
    I can’t imagine how big it will get in a month or so. I know it is possible to set auto purge to a desired amount of days but this plugin would be useless if I couldn’t see my statistics for last 30 days at least (my database would still be around 750MB and that is huge).
    This really is a problem. Everybody wants to have the smallest database possible since it decreases server load blah, blah, blah… Also, it is a problem when I backup my website. I have automated daily backups (I can’t exclude slimstat tables from it) and this would add some 750MB to every backup (if I set auto purge to 30 days which still isn’t enough). Database would be bigger than all files on my server (and I have 10k images on my website).
    Now the suggestion: I believe that it would be better if all data was stored in a separate database. That way, the wordpress database wouldn’t be impacted and wordpress could be manipulated separate from the data slimstat collected. I will have to disable this plugin the way it is now and I’m sure I’m not the only one.
    Best regards,
    Teodor

    https://www.ads-software.com/extend/plugins/wp-slimstat/

Viewing 9 replies - 1 through 9 (of 9 total)
  • Plugin Author Jason Crouse

    (@coolmann)

    Thank you, Teodor.

    This is indeed one of the add-ons that we have on our todo list. You are more than welcome to contribute with your own code, if you already have something ready.

    Best,
    Camu

    Plugin Author Jason Crouse

    (@coolmann)

    Just a quick follow-up on this. Version 3.3, which has just been released, implements this feature, now. Would you be interested in testing it? I can send you a prototype of the add-on…

    Thread Starter teodorsavic

    (@teodorsavic)

    Hi Camu.
    Thank you very much but I stopped using this plugin after a few days. My database started to grow very fast so I decided to disable it.
    Anyway, this is a great plugin. I wish you all the best in developing and upgrading it.

    I’d be willing to test it if you are still looking for testers…

    Plugin Author Jason Crouse

    (@coolmann)

    Teodor,

    Thank you for your encouraging words. WP SlimStat’s tables have been designed with optimization in mind. But I agree that this plugin may not suitable for very trafficked websites. Unless you setup a dedicated mysql server to it (starting from 3.3).

    Ovidiu,

    Thank you for your availability. Contact us through our website, and I will send you both the dev version of SlimStat and the add-on that allows you to select a different database.

    Best
    Camu

    Plugin Author Jason Crouse

    (@coolmann)

    Ovidiu, I have a prototype ready. Contact us so that I can send you a copy.

    Camu I don’t think I’m the right person to test anymore as I’ve switched over to Piwik.
    Seemed less a hassle to manage ONE single stats tool rather than manage Wp Slimstat on 20 different WP sites. Nothing to do with the performance of WP Slimstat just trying to cut down on management-time.

    Plugin Author Jason Crouse

    (@coolmann)

    Well, I’m sorry to see you go.

    Hi Camu,

    Scenario A:

    A possible solution is to create a routine which the admin can capture the past data then archive that to a spread sheet file – then it can be purged. Any intense data logging from any script, will increase the database size. This is not a SlimStat issue, this is fact if you want intense reporting. The more detailed the data, the larger the database. What makes SlimStat attractive is the detailed tracking. Detailed reporting has its penalty – increased size of the database.

    Scenario B:

    Provide the means where the admin can toggle off/on reporting instances. This would allow detailed reporting for a campaign for one site while keeping SlimStat’s reporting of other domaina/servers to a minimum. The default reporting setup for this plugin would be set to a minimum reporting.

    Scenario C:

    Always allowing the admin to toggle off/on stat instances, create the option to utilize an XML file for stat data. This would not impact the WordPress database server. This would allow you to export to other formats. SlimStat would be a hybrid of MSQL for WordPress for basic plugin data and XML for the stats.

Viewing 9 replies - 1 through 9 (of 9 total)
  • The topic ‘Database suggestion’ is closed to new replies.