![]() ![]() I not sure but revisiting the performance of the pixel engine might be a interesting thing to do. Even thou it should be Multi-threaded, while the Smudge is Single threaded. It really is a matter of RAM?įor me I find that the new Smudge engine is smoother/faster than the Pixel Engine, when the Pixel Brush has all of the following: various options enabled (rotation, size, scatter) and it has textures. You can see a neat site that explain this in more detail (for linux in specific): Linux ate my RAM Letting free memory marked as being reserved, but at the same time being available to any other application to use it. This is why there isn’t much we can do, it is a behavior of the OS. ![]() The 1.8 Gb extra is free to any other application to use, and Krita will not use it as it already has a ‘true’ 4 Gb limit being used. In your example: Krita can only have 4 Gb, but the task manager says 5.8 Gb. The thing is, if another program need the RAM is the OS the one responsible of getting the ‘over allocated’ memory from Krita to the new program. However the OS(Windows, Linux, Mac) will let free memory to be ‘reserved’ to certain applications.īasically, instead of reusing free memory that Krita already let go of (what you called garbage collection), the OS gives krita a ‘new’ portion of memory and the ‘old’ unused one keeps being marked as used (or reserved) to Krita in the task manager. ![]() Krita will use only the memory that you allowed it in the settings. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |