![]() Registered Member ![]()
|
I've read through most of this topic and now I'm making this post to see if anyone can help me determine the cause of slowdown for my specific machine.
My basic system specifications are:
Like some people described in the thread I link at the start, Krita has general slowdown in most interactions I have with its features. The startup isn't that slow for me, about 15-17 seconds (until I can interact with menus). But creation of a new canvas takes about 10-12 seconds and some brushes are quite laggy/delayed (some brushes, even just switching to eraser mode, can cause the program to hang). I can live with these slowdowns, but if there was a way I could solve them, that'd be great. ![]() I have enabled logging for Krita, although I'm not sure where to find the logs. Also, I accidentally typed an extra g at the end of my nickname here. Edit: This has been fixed, thanks to a forum admin. ![]()
Last edited by NerArth on Tue Jan 26, 2016 9:37 pm, edited 1 time in total.
|
![]() Registered Member ![]()
|
Hi, I see you are using AMD, so it might worth to try newly added "Disable Vector optimizations(for AMD CPUs)" in Settings - > Configure Krita -> Performance. I hear that Vector optimization is not working well with AMD CPUs, so there is this option to turn it off.
Other than that(and usual tweaking OpenGL settings like texture buffer on/off, filtering method), I do not have an extra idea... (As for your forum name, you might be able to ask forum admins to sort it out. Their contact is in the bottom of the pages) |
![]() Registered Member ![]()
|
Thank you for taking the time to reply to my post. I have been using "Disable Vector optimizations (for AMD CPUs)" for a while now, as you suggested, and unfortunately I've not really noticed an improvement with it. I tried the OpenGL texture buffer toggling and I've not noticed any improvements from it being either on or off, but it suggests to have it off for AMD stuff, so currently I have it off. The most annoying issue I have really is the slowness when toggling the eraser mode with certain brushes, but I've just learned to avoid using them for that reason. ![]() How much memory should I be actually giving to Krita? Could RAM and its speed settings be an issue? I think my RAM is supposed to run at 1833MHz but I think it has to run at 1600MHz currently. I'm sorry for being so verbose, I just want to understand what my issue might be. (Perhaps other than the fact I'm using windows ![]() |
![]() KDE Developer ![]()
|
With AMD they mean AMD graphics cards.
Canvas creation speed has to do with the bit-depth of the canvas(I don't exactly know why, though) and brush speed can be affected by it as well. For increased brush speed, test out the 3.0 alpha. Eraser mode is known bug, but no idea why that happens either. It is very difficult to diagnose slow-down, and it has been the case that we had users complain about slowdowns in places that we would not dream of going because of how obvious it is to us that this would cause a slowdown(For example, a 32bit float colorspace is going to cause slowdowns, so are 16 filter layers on an image, but apparently this is not obvious to all users). Logs should be in your working directory, which on linux is the home directory, or the directory of the image you loaded. Search for a folder named 'log' or 'logs'. |
![]() Registered Member ![]()
|
Ah, I see.
Thank you, that's good to know; I'll give the alpha a try some time this week.
I can understand it's a difficult thing to do, but I can give you some of my normal parameters, if it's helpful; I usually create images in a 16:9 ratio, either at 480x270 or 1920x1080 (and sometimes double of that, but I haven't done for some time). Additionally, I always create them as 8-bit colourspace and I rarely have more than 10 layers in a single file, and I don't use Krita's filters, as I leave that kind of thing to another program. As for the logs, the "...\Krita\log\" folder has logs for each of the brushes (or something of the sort); the log file ending is .rdata and .kpp. Is this the kind of log we want? Edit: I think that when I try the alpha I'll try to clean my settings out too, because recently a strange issue, which is unrelated to this topic, has cropped up. |
Registered users: abc72656, Bing [Bot], daret, Google [Bot], lockheed, Sogou [Bot], Yahoo [Bot]