I am back from the PGCon 2015 and was fortunate enough to present my first paper on "Native Compilation" technology. Also got opportunity to meet most creamy folks of PostgreSQL community, found everyone to be very polite and easy to go.
As part of this Native Compilation technology, I mostly focused on the Native Compilation of Relation, which we call it as Schema Binding.
Some of the details from presentation are as below (For complete presentation please visit Go Faster With Native Compilation):
Native Compilation:
Native Compilation is a methodology to reduce CPU instructions by executing only instruction specific to given query/objects unlike interpreted execution. Steps are:
As part of this Native Compilation technology, I mostly focused on the Native Compilation of Relation, which we call it as Schema Binding.
Some of the details from presentation are as below (For complete presentation please visit Go Faster With Native Compilation):
Native Compilation:
Native Compilation is a methodology to reduce CPU instructions by executing only instruction specific to given query/objects unlike interpreted execution. Steps are:
- Generate C-code specific to objects/query.
- Compile C-code to generate DLL and load with server executable.
- Call specialized function instead of generalized function.
Schema Binding:
Native Compilation of relation is called the Schema Binding. Since most of the properties of a particular remains same once it is created, so its data gets stored and accessed in the similar patter irrespective of any data. So instead of accessing tuples for same relation in generic way, we create a specialized access function for the relation during its creation and the same gets used for further query containing that table.
It gives performance improvement of upto 30% on standard TPC-H benchmark.
