query

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

2.

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

34 points•fanf•4 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•10 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.

21 points•ajoski9•about 2 months ago•15 comments•
7.

Most of the time, you’ll hear advice that you should select as few columns as possible so that SQL Server can do less work. However, one of my clients hit a neat edge case scenario where SELECT * queries actually…

9 points•pek•almost 7 years ago•0 comments
8.

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

8 points•Clickin•2 months ago•3 comments•
10.

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

5 points•sylq•7 months ago•1 comment
11.

One lens I've found satisfying for "what is a query planner" is that it's a tool for "approximating domain knowledge." By that I mean, someone who knows...

5 points•eatonphil•about 3 years ago•0 comments
12.
4 points•UncleOxidant•about 2 months ago•1 comment•
13.

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

4 points•charles_irl•about 2 months ago•1 comment•
15.

OpenStreetMap data extracted into thematic layers and converted to cloud-native file formats that are easy to use with software from DuckDB to QGIS.

3 points•raybb•about 2 months ago•0 comments•
16.

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

3 points•hyzyla•2 months ago•0 comments•
17.

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•over 5 years ago•0 comments
18.

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•about 2 months ago•0 comments•
19.

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

2 points•charles_irl•about 2 months ago•0 comments•
20.
2 points•ibobev•about 2 months ago•1 comment•
21.

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•about 2 months ago•0 comments•
22.

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•about 2 months ago•0 comments•
23.
2 points•jruohonen•2 months ago•0 comments•
24.
1 points•vinhnx•about 2 months ago•0 comments•
25.

Master ClickHouse query optimization through architectural understanding. Learn why ORDER BY design can improve performance 100×, plus proven techniques for trillion-row millisecond queries.

1 points•costco•about 2 months ago•0 comments•
26.
1 points•birdculture•about 2 months ago•0 comments•
27.
1 points•fanf2•about 2 months ago•0 comments•
28.

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•about 2 months ago•0 comments•
29.

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•about 2 months ago•0 comments•
30.

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

1 points•hollylawly•about 2 months ago•0 comments•
31.

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•about 2 months ago•0 comments•
32.

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

1 points•birdculture•about 2 months ago•0 comments•
33.

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

1 points•softwaredoug•2 months ago•0 comments•
34.
1 points•relatedcode•2 months ago•0 comments•

Related topics