-
### Describe the bug
With all drivers we wait for the query to return from the DB, and if the user leaves the page or the connection gets cut, the backend stops the query.
BigQuery doesn't seem to…
-
## Bug Report
Please answer these questions before submitting your issue. Thanks!
### 1. Minimal reproduce step (Required)
```sql
select time,query from information_schema.cluster_slow_query…
-
We need to have a number of alarms setup for all envs:
- [x] Slow running DB queries > 1s
- [x] Memory utilisation for containers > 80%
- [x] CPU utilisation for containers > 90%
- [ ] Long runn…
-
After some time of usage, the dashboard becomes very very slow, up to the point of queries timing out.
I found these two indices help:
```SQL
ALTER TABLE email_event ADD INDEX timestamp (timest…
-
**Is your feature request related to a problem? Please describe**
I am currently running a DD instance with 200k active findings. The findings DB table currently has nearly 7.5m rows. Day for day, my…
-
Problems:
- Accuracy: The more data we add, the higher the probability of having results being missed.
- Performance: Might lead to load spikes at the server.
- Storage: Consumes lots of space in t…
-
edit from @lostmygithubaccount: we'll re-purpose this issue to investigate the q2 performance issue noticed below and the "one billion row challenge" performance issue noticed w/ the Polars backend. I…
-
Since policy events are handled one-by-one from the all stream, there is a possibility for a policy to severely lag behind if slow queries are used in the policy handler. My current solution is to ha…
-
Flux queries involving `keep() |> aggregateWindow` or `drop() |> aggregateWindow` are slower than their InfluxQL equivalents. This issue is to optimize the Flux queries to be on par with InfluxQL.
…
-
Scrolling feels slower than necessary. For a large part this is due to how we handle it now:
- we buffer scroll events and wait for a timeout (couple of hundred milliseconds)
- when the timeout ex…