Hola @ricardorvm,
Thank you for taking the time to provide us with detailed feedback. We’re genuinely sorry to hear about the issues you’ve faced.
Concerning CPU consumption, it’s important to note that any locally hosted analytics plugin, including ours, will result in more CPU usage because each visitor’s actions have to be logged. For websites with large traffic volumes like yours, this can add up.
In addition, the nature of locally hosted analytics means that the database will inevitably grow over time as more visitor data gets stored. This is a trade-off for the increased privacy and control that local hosting offers.
We are continually working to optimize Burst’s performance and are focusing on reducing database sizes. In fact, we already have an archiving function that should help manage the database size over time.
We have plans for an upcoming version that can be installed on a separate server. This will ensure that the CPU of your main website is not affected by our plugin.
We regret that you’ve had to uninstall our plugin. However, your insights are invaluable to us as we strive to make Burst better.
If you value handling user data privacy on your own server and wish to contribute to our free, open-source project, we would be happy to collaborate with you on a solution for your specific use case.
Kind regards,
Hessel