Madu Mitha Ravi comments

Results 33 comments of


                                            Madu Mitha Ravi

Last value Cache - Increase in outliers beyond 16 threads for 100 series

@hiltontj Below are traces from the similar query that differs only by the tag value/where clause. `SELECT * FROM last_cache('senec_data', 'ntag1-lv-1') where device_id in (....);` - No concurrency - 14...

Last value Cache - Increase in outliers beyond 16 threads for 100 series

yes, that is right.

Last value Cache - Increase in outliers beyond 16 threads for 100 series

@hiltontj Results with exact 100 series in the where clause for Last value cache. Query: `SELECT * FROM last_cache('senec_data', 'ntag1-lv-1') where device_id in (....);` where IN has 100 values. Query...

Last value Cache - Increase in outliers beyond 16 threads for 100 series

## Latest Last value cache results on PRO - Dec 12th ### Large machine configuration ### 8XL machine configuration **To investigate:** @hiltontj - Why are we getting limited at 3...

Last value Cache - Increase in outliers beyond 16 threads for 100 series

@hiltontj If you do have any configurations in mind (tokio, IO threads etc.), I can try them and share the numbers.

Last value Cache - Increase in outliers beyond 16 threads for 100 series

### Latest results of Last value cache with concurrency - Jan 7th #### Key Observations - The graph shows that when there is room for CPU & Memory but they...

Last value Cache - Increase in outliers beyond 16 threads for 100 series

Yes, the concern still exists, below are the latest numbers. - The Last value cache with concurrency are executed across two datasets 17 rows/sec and 1k rows/sec on 4ENT where...

Last value Cache - Increase in outliers beyond 16 threads for 100 series

Thanks @hiltontj , I would like to keep this open until then.

Last value Cache - Increase in outliers beyond 16 threads for 100 series

Here are the latest results, this concern still persists. - Queries per second stagnates with increase in concurrent threads of queries - Resources are not exhausted, CPU and Memory are...

Monolith OSS - Limit query consumes high CPU usage for look backs 12+hours

@pauldix Here are the explains. Explains for Q5 query (LIMIT 5 reaching CPU usage of 93%) plan: Sort: senec_data.time DESC NULLS FIRST, fetch=5 Filter: senec_data.device_id = Dictionary(Int32, Utf8("136")) AND senec_data.time...