305% performance improvement with python bindings #299
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
(Addresses #287)
There are probably many better ways of doing this than adding a field to
hb_glyph_position_tbut as a proof of concept, it is possible to achieve a roughly 300% increase in speed by having the glyph info/position lookups resolved in C rather than in Python through GObject.This reduces the number of python attribute lookups required from 4 to 1 per glyph. Since sticking the values into the
hb_glyph_position_tstruct probably isn’t the best way to go, if there was a way to generate the array independently, testing shows it would probably achieve close to a 1000% percent performance improvement (since the bottleneck is still the one python attribute lookup).