• Resolved davidki

    (@davidki)


    Hello, I have two questions for you:

    1.
    I read that you have plan that your plugin can be installed on a separate server.

    Is it possible right now? If not, when might it be?

    2.
    Your plugin, same as other analytical plugins, store a large amount of data and thus the database will grow quickly.

    Does your plugin use data aggregation? If not, can you add it? I think it can save decent amount of database space.

    For example plugin “Koko Analytics” use data aggregation.

    Thank you,

    david

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Author Hessel de Jong

    (@hesseldejong)

    Hi David,

    1. We don’t have an exact date yet for installing it. We could send you an email/message when we have a beta version ready. This way we can help guide you and resolve issues quickly.
    2. Yes we do aggregate and summarize a lot of data. But we do still allow a lot of filtering, which requires more data. I am thinking about a setting that allows you to collect more data and filter more or collect less and filter less. So we can keep everyone happy. But this is something I have to discuss with the team.

    Hope this answered your question!

    Kind regards,
    Hessel

    Plugin Author Rogier Lankhorst

    (@rogierlankhorst)

    @davidki You can use this branch https://github.com/Burst-Statistics/burst/tree/combine-files

    It combines the inline variables and the burst script into one file, if the setting is enabled. Apart from that, you can add the constant

    define('BURST_HEADLESS', true);

    So the tracking script is not enqueued on the separate server itself.

    The only thing you then have to do is to embed the javascript on the site that you want to track.

    That said, if you just copy over the inline variables, and the javascripts added by burst, you can track statistics with the current version as well.

    In addition to what Hessel said, you can auto archive or delete older data in the plugin, which can help to keep your database small(er).

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Database efficiency and size’ is closed to new replies.