Database size grows large due to site usage entries
2 posts · Closed
Dear Networx developers,
Thank you very much for providing support!
Currently, when "ignore LAN traffic" is enabled to provide app/site usage monitoring, the database can grow quite large, in which "siteusage" is a major contributing factor.
For example, the number of entries in each table in the database accumulated in half a year (1.7 GB) is as follows:
appname: 80 entries
appusage: 42393 entries
sitename: 4548376 entries
siteusage: 8118609 entries
appsiteusage: 7817897 entries
The tables related to site usage are enormous, taking up the majority of space. Even deleting or dropping such a big table can take literally days to complete. For those who only need to monitor application usage, an option to not write site usage into the database can be quite helpful to keep database size in control. Also the CPU stress from the filtering mechanism might reduce if site usage calculation is disabled.
Thanks in advance!
Thing is, NetWorx was not originally designed to monitor apps. This functionality has been added over time, and even though it works, it's rather clumsy. There are a few CPU and storage usage issues as well.
With this in mind, we have built a new app called NetGenius. It is basically a simplified and optimised version of NetWorx, designed specifically for monitoring apps. Its database storage is compact and CPU usage is low, and we now recommend using NetGenius instead of NetWorx for application monitoring.
You are welcome to download NetGenius and take a look.