[ Thread Index |
Date Index
| More lists.liballeg.org/allegro-developers Archives
]
On 2009-07-28, Paul Suntsov <siegelords_abode@xxxxxxxxxx> wrote:
> I've traced down the problem (at least on my machine) to the
> invocation of FT_Load_Glyph. According to the FreeType documentation
> this function is very slow, and removing its call from the addon sped
> up ex_ttf 3-4 times for me. The only thing we use FT_Load_Glyph during
> normal operation (i.e. after we cached the glyph) is to get the new
> advance values. I figured that there should be no problem in caching
> these advance values, so that FT_Load_Glyph call can be eliminated. In
> my testing I did not see any apparent difference between cached and
> non-cached versions of the code, while seeing significant speedup:
> ex_ttf went from 150 FPS to 550 FPS for me. The diff is attached.
It sounds like a different problem as Matthew reported that the problem
was present with ex_font.c, which uses bitmap fonts, and the profile
suggested software rendering was the culprit.
Still, it sounds like your patch is a good optimisation.
Peter