Troubleshooting High CPU and Memory Usage in Zinc Service
TLDR Zygimantas experienced high CPU and memory usage in zinc service while querying large datasets. Hengfei offered suggestions to optimize and test for local disk and S3 usage. Gaby and Prabhat discussed SIMD tag performance.
May 19, 2023 (1 week ago)
RAM 64 GB DDR4
Disk:2 x 512 GB NVMe S
Compressed Size 38,210 MB
set the memory cache limit to 20GB, and then query all data again, to see if it can work.
or, set a small size:
or in the server side, you also should see some error.
Improving CPU Utilization During Bulk Ingestion in Zinc
Ayush experiences high CPU usage during bulk ingestion in Zinc and seeks optimization. Hengfei recommends adjusting the flush WAL to index interval. Ayush doesn't see significant improvement, requests sync API, but none is available.
ZO Kubernetes Issues: Query Log Error and Adding Users
Sa had issues with querying logs in ZO on Kubernetes and creating users. Hengfei provided solutions for both problems, including updating with a dev version and setting memory cache values.
Vector Crashes with Timeouts during ZO Ingestion
Gaby experienced Vector crashes and timeouts during ZO ingestion. Prabhat suggested disabling alerts, and Gaby found better performance without alerts and by adjusting batch and buffer settings.
Integrating ZincObserver and Resolving Log Issues
sparrow faced issues with ZincObserver integration, log filtering, and missing logs. Ashish and Hengfei provided solutions, including using str_match and an updated image. A future release will provide more error responses for ingestion.
Elasticsearch vs Zinc for 40TB Dataset
Josh asks if zinc works for a 40TB dataset. Prabhat replies that zinc is not suitable due to single node limitation but suggests using zinc-observe for petabyte scale data.