![]() ![]() Valgrind -tool=callgrind -instr-atstart=no krita Unless the thing you’re trying to optimize is the program startup, you can tell valgrind to run with the logging, or instrumentation, turned off at start: For example, you may want to only monitor the performance when drawing a stroke. ![]() ![]() You can tell callgrind to focus only on the part of the code you want to optimize. Gradients are calculated on load, instead of being associated with a PNG preview image that is cheap to load Pigment preloads all profiles (startup hit) Projection recomposition doesn’t take the visible area into account Tile engine 1 has the BKL tile engine 2 cannot swap yet and isn’t optimized yet The calculation of the mask for the autobrush is very slow and doesn’t cache anythingĬaching a whole row or column of tiles in the h/v line iterators should speed up things a lot The histogram docker calculates even when hidden Optimizing tips and tools for Krita ¶ Hot Spots ¶ ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |