![]() ![]() ![]() The TPC-H benchmark Q1 query is a good candidate for measuring the impact of the new executor stack at its best, so that’s the one we’re using here. the query is complex enough to warrant spending JIT efforts on it.Ī query that fetches some information over a primary key surrogate id would not be a good candidate to see the improvements given by the new JIT infrastructure in PostgreSQL.the query reads a fair amount of data but isn’t starved on IO resources.the query contains several complex expression such as aggregates.The JIT expression compiler currently works best in the following situation: One of the things I love about my engineering work at Citus Data working on scaling out PostgreSQL with the Citus extension is that I get to run benchmarks! Benchmarks are a great tool to show where performance improvements provide a benefit. Andres has been working on this part of the system for a while now, and in the next release we are going to see a new component in the execution engine: a JIT expression compiler! Benchmarks and TPC-H One of the big changes in the next PostgreSQL release is the result of Andres Freund’s work on the query executor engine. In the meantime, testing it with your own application is a great way to make sure the community catches all the remaining bugs before the dot-zero release. PostgreSQL 11 is brewing and will be released soon. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |