Probably should look at one of the profile guided binary layout optimizers (e.g.facebook's bolt) and see how much that helps. But I think we also need to look at why our code density/locality is so shitty that we get such a huge number of faults.https://twitter.com/AndresFreundTec/status/1214305610172289024 …
Re low code locality (in query processing, in particular): Possibly a consequence of PostgreSQL's adoption of the Volcano iterator model?
-
-
That's a problem, but not in the workload I was testing. The query executor itself only takes up a small percentage of the time in a readonly, fully cached, pgbench -S workload.
-
I think it's more that there's traversal through quite a few layers when processing a query (network handling, protocol handling, query execution initialization, query execution, protocol handling, network), and they're all one or more C translation units.
- Još 2 druga odgovora
Novi razgovor -
Čini se da učitavanje traje već neko vrijeme.
Twitter je možda preopterećen ili ima kratkotrajnih poteškoća u radu. Pokušajte ponovno ili potražite dodatne informacije u odjeljku Status Twittera.