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

Query log filtering very slow on underpowered devices such as routers #5367

Open
3 tasks done
timkgh opened this issue Jan 16, 2023 · 7 comments
Open
3 tasks done

Query log filtering very slow on underpowered devices such as routers #5367

timkgh opened this issue Jan 16, 2023 · 7 comments
Labels
waiting for data Waiting for users to provide more data.

Comments

@timkgh
Copy link

timkgh commented Jan 16, 2023

Prerequisites

  • I have checked the Wiki and Discussions and found no answer

  • I have searched other issues and found no duplicates

  • I want to report a bug and not ask a question

Operating system type

Linux, Other (please mention the version in the description)

CPU architecture

64-bit MIPS

Installation

GitHub releases or script from README

Setup

On a router, DHCP is handled by the router

AdGuard Home version

v0.107.21

Description

Filtering the query log on an EdgeRouter ER-12 is very slow and causes very high CPU use. This means I can't really keep more than 7 days of logs and have a usable UI.

@ghost
Copy link

ghost commented Mar 27, 2024

Hi there, are you still experiencing this?

@ghost ghost added the waiting for data Waiting for users to provide more data. label Mar 27, 2024
@overwatch3560 overwatch3560 added cannot reproduce and removed waiting for data Waiting for users to provide more data. labels Apr 2, 2024
@overwatch3560 overwatch3560 closed this as not planned Won't fix, can't repro, duplicate, stale Apr 2, 2024
@timkgh
Copy link
Author

timkgh commented Apr 2, 2024

Hi there, are you still experiencing this?

Yes, nothing changed, still slow. Can you please reopen?

@overwatch3560 overwatch3560 added waiting for data Waiting for users to provide more data. and removed cannot reproduce labels Apr 2, 2024
@overwatch3560
Copy link

What do you mean with very slow?

@timkgh
Copy link
Author

timkgh commented Apr 3, 2024

What do you mean with very slow?

It takes minutes to get any results when I click on the Dashboard > Blocked malware/phishing
E.g. this URL: https://192.168.1.1/#logs?response_status=blocked_safebrowsing

@ainar-g
Copy link
Contributor

ainar-g commented Apr 3, 2024

This is likely just an inevitable consequence of having to filter through a lot of data fetched from the disk. See #2290.

You can enable verbose logging to see the progress of the fetching and filtering. It is likely that it's just inherently slow on that hardware, and in that case the recommendation would be to limit the size of the querylog or, if RAM allows, keep it in memory.

@ainar-g ainar-g reopened this Apr 3, 2024
@Cebeerre
Copy link

Cebeerre commented Apr 3, 2024

What do you mean with very slow?

It takes minutes to get any results when I click on the Dashboard > Blocked malware/phishing E.g. this URL: https://192.168.1.1/#logs?response_status=blocked_safebrowsing

Assuming you're using OpenWRT on this Uniquiti router, are you using the squash image so all the "/data" AGH directory is sitting on the ramdisk ?

@timkgh
Copy link
Author

timkgh commented Apr 3, 2024

I'm using EdgeOS, not OpenWRT, but all the AGH logs are in /tmp (tmpfs) mainly to no wear the flash. Keeping only 14 days of logs (7 days rotation), ~125MB and it's still very slow.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
waiting for data Waiting for users to provide more data.
Projects
None yet
Development

No branches or pull requests

4 participants