Large stats.db causes slowdowns in DNS lookups #2753

New issue

Open

opened 2026-03-04 02:19:24 -05:00 by deekerman · 1 comment

deekerman commented

2026-03-04 02:19:24 -05:00

Owner

Originally created by @PLight14 on GitHub (May 8, 2021).

Originally assigned to: @ainar-g on GitHub.

I have Adguard home running on a Synology NAS (HDD, no SSD). The switch from 105.2 to 106 caused dns lookup delays that did not appear in the lookup times in the query log. Websites would hang on DNS lookup for a few second. However, after clearing the history (deleting the 25mb stats.db) the delays were gone again.

This probably has something to do with a relatively slow insert (or equivalent) in the SQLite DB when it increases in size.

Originally created by @PLight14 on GitHub (May 8, 2021). Originally assigned to: @ainar-g on GitHub. I have Adguard home running on a Synology NAS (HDD, no SSD). The switch from 105.2 to 106 caused dns lookup delays that did not appear in the lookup times in the query log. Websites would hang on DNS lookup for a few second. However, after clearing the history (deleting the 25mb stats.db) the delays were gone again. This probably has something to do with a relatively slow insert (or equivalent) in the SQLite DB when it increases in size.

deekerman added the

research

needs investigation

performance

labels

2026-03-04 02:19:24 -05:00

deekerman commented

2026-03-04 02:19:44 -05:00

Author

Owner

@ainar-g commented on GitHub (May 11, 2021):

Hello. The file isn't an SQLite database, unfortunately, but a BoltDB one. This is tangentially related to #2290, as we've been struggling to fine a performant, portable, reliable, and pure-Go database format. We have some experiments in the works, but unfortunately I cannot give any guarantees for now.

In the mean time, we'll probably need to be smarter about how we update statistics and its impact on the overall performance. Perhaps the DB's schema needs some rethinking as well.

@ainar-g commented on GitHub (May 11, 2021): Hello. The file isn't an SQLite database, unfortunately, but a BoltDB one. This is tangentially related to #2290, as we've been struggling to fine a performant, portable, reliable, and pure-Go database format. We have some experiments in the works, but unfortunately I cannot give any guarantees for now. In the mean time, we'll probably need to be smarter about how we update statistics and its impact on the overall performance. Perhaps the DB's schema needs some rethinking as well.

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/AdGuardHome#2753

No description provided.

Rows
Columns