Replies: 3 comments 37 replies
|
Would you mind running Currently, we can't use index to accelerate |
|
Ok, I think we have made progress. I modified my config file: default_timezone = "America/Los_Angeles"
max_in_flight_write_bytes = "8GB"
## The maximum current queries allowed to be executed. Zero means unlimited.
max_concurrent_queries = 0
## Enable telemetry to collect anonymous usage data. Enabled by default.
enable_telemetry = false
[storage]
data_home = "/greptimedb_data"
type = "File"
[logging]
dir = "/greptimedb_data/logs"
log_format = "json"
[[region_engine]]
[region_engine.mito]
num_workers = 2
max_background_flushes = 1
max_background_compactions = 1
max_background_purges = 1
max_concurrent_scan_files = 600
scan_memory_limit = "80%"
scan_memory_on_exhausted = "wait(15s)"
experimental_compaction_memory_limit = "12GB"
experimental_compaction_on_exhausted = "fail"I'm seeing fewer usage spikes, and when the spike is too large for too long, I see the compaction job canceled. The newest memory profile in the attached zip shows what I currently see when the ram is spiking. |
|
We found some files have very large blobs, so it took a lot of memory to compact them. So this is expected. You can keep the compaction memory limit to avoid OOM. We also implemented a fix to skip large tasks early if possible recently. I think it'd be helpful to expose max_row_group_uncompressed_size to the ssts_manifest. |
Uh oh!
There was an error while loading. Please reload this page.
I finally have time to work on my Greptime stuff again. Specifically I need to pull out log data about a service so we can figure out what to do with it.
The issue is that as soon as I start querying more than 2 days of data, the query times out. Since I do keep running into this issue when examining other data as well, I'd like to learn how to optimize/fix/etc whatever I need to in order to do what I want.
Setup is greptime/greptimedb:v1.0.0-rc.1 docker image running on a dedicated vm with 24gb of ram and 4 vcpu.
Storage is local pointed at an iscsi volume living on a flash array.
Grafana is 12.3 via a container on a different host. Both vms/hosts are in the same network/hypervisor.
I have a traefik proxy instance in front of GreptimeDB.
In grafana, my queries are:
I just added indexes on a couple columns, and that helped a bit. It wasn't working for more than a few minutes worth of data before, and after it started working up to 2 days worth.
I am applying some transformations in grafana, but my timeout errors don't occur via my browser crashing, so it shouldn't be the processing of those, right?
Anyone have any tips?
All reactions