Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

high I/O usage while generating reports, and running out of inodes #434

Open
iamdue opened this issue Feb 21, 2020 · 3 comments
Open

high I/O usage while generating reports, and running out of inodes #434

iamdue opened this issue Feb 21, 2020 · 3 comments
Assignees
Milestone

Comments

@iamdue
Copy link

iamdue commented Feb 21, 2020

As dnssafety stores the reports in files, it ususally generates high I/O usage on the virtual machine it runs on, while generating it's reports.
Also we run out of inodes because of storing everything in little files.
I wrote a cron to delete reports older than 15 days, to free up inodes, but the deleted reports are recreated every day. Is it possible to set report range that should be stored, or to store data in SQL?

@ra-at-diladele-com ra-at-diladele-com self-assigned this Feb 21, 2020
@ra-at-diladele-com ra-at-diladele-com added this to the 0.X Future milestone Feb 21, 2020
@ra-at-diladele-com
Copy link
Contributor

May I ask how many users/ips are directed to the dnssafety server? What is the size of the /opt/dnssafety* folders?

@iamdue
Copy link
Author

iamdue commented Mar 1, 2020

Nearly 100 users are using the server. And the size of folders 3.2G. I also have to mention that I am now deleting reports and stats older than 15 days with a cron.

@groninge01
Copy link

I also have the same problem on a RPI. I am using it on my home network and I only have 9 devices using it.

278M /opt/dnssafety
1.2G /opt/dnssafety-ui

I have deleted some reports and access.logs to free up space.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants