query

26 stories and discussions about query, aggregated from every source we track.

1.

The reason for and design of Krabby's query system.

34 points•fanf•about 2 months ago•9 comments
3.

After a user signaled a performance issue in a Matrix client, we have added new tracing timers in the Matrix Rust SDK to spot the problem. Once found, we have fixed an SQL query improving the throughput from 19k to…

28 points•sknebel•about 1 year ago•0 comments
4.

Implementing an LSP from our query-based compiler passes

22 points•polywolf•8 months ago•7 comments
5.

High-performance, AI-safe self-service analytics — a governed semantic layer fused with beautiful-by-default dashboards, for humans and agents.

18 points•ajoski9•about 10 hours ago•8 comments•
7.

Write SQL. Keep TypeScript. Skip the query-builder translation layer. - Clickin/SQLBraid

8 points•Clickin•10 days ago•3 comments•
9.

Contribute to chrishayuk/larql development by creating an account on GitHub.

5 points•sylq•6 months ago•1 comment
10.
4 points•UncleOxidant•about 20 hours ago•1 comment•
11.

Maximizing perf on AI-SQL queries with the KV-optimal left-deep join

4 points•charles_irl•4 days ago•1 comment•
12.

Kibana/ES CLI for logs. Contribute to hyzyla/kibana-agent development by creating an account on GitHub.

3 points•hyzyla•11 days ago•0 comments•
13.

At Community.com, we had a problem where a bunch of workers needed to pick up and process a large amount of data fr…

3 points•relistan•about 5 years ago•0 comments
14.

Maximizing perf on AI-SQL queries with the KV-optimal left-deep join

2 points•charles_irl•1 day ago•0 comments•
15.
2 points•ibobev•1 day ago•1 comment•
16.

How do Postgres providers handle a query that exhausts memory? A recursive query benchmark compares query failures and cluster survival across ClickHouse Managed Postgres, Cloud SQL, PlanetScale, and Amazon RDS.

2 points•saisrirampur•2 days ago•0 comments•
17.

Across 244 query shapes on identical servers, Oliver was 3.06 times faster than ClickHouse at the median, and it ran all of them in less time than ClickHouse took to load the data.

2 points•pnr-consulting•3 days ago•0 comments•
18.
2 points•jruohonen•8 days ago•0 comments•
19.
1 points•fanf2•about 16 hours ago•0 comments•
20.

How do Postgres providers handle a query that exhausts memory? A recursive query benchmark compares query failures and cluster survival across ClickHouse Managed Postgres, Cloud SQL, PlanetScale, and Amazon RDS.

1 points•saisrirampur•1 day ago•0 comments•
21.

When agentic sessions run to a million tokens with many sessions resident at once, the KV cache and the index that ranks it live in host memory, and the scan that ranks all n keys for a top-k step becomes the traffic…

1 points•vivekkalyanaran•1 day ago•0 comments•
22.

Follow a SQL query through the router, across four Postgres shards, and back.

1 points•hollylawly•1 day ago•0 comments•
23.

Your CI database picks different plans than production because its statistics differ. Inject production stats with PostgreSQL 18, or generate rows that carry the distribution. Here is how to tell which one you need.

1 points•ammarmalik17•2 days ago•0 comments•
24.

Maximizing perf on AI-SQL queries with the KV-optimal left-deep join

1 points•birdculture•3 days ago•0 comments•
25.

Kicking the tires of jev for a very basic query understanding task

1 points•softwaredoug•7 days ago•0 comments•
26.
1 points•relatedcode•9 days ago•0 comments•

Related topics