https://bugs.kde.org/show_bug.cgi?id=456998

            Bug ID: 456998
           Summary: Performance degrades heavily over time, RAM usage
                    peaks at 11GB.
           Product: krita
           Version: nightly build (please specify the git hash!)
          Platform: Microsoft Windows
                OS: Microsoft Windows
            Status: REPORTED
          Severity: normal
          Priority: NOR
         Component: General
          Assignee: krita-bugs-n...@kde.org
          Reporter: i...@ralek.art
  Target Milestone: ---

I draw for 5-8 hours at a time, generally. I notice significant performance
decreases over time, peaking at around the 2 hour mark and then remaining.

Upon opening Krita and a medium size document, memory usage is around 2.3gb.
After several hours of drawing, this peaks at around 11GB. I've never seen it
go much over that, regardless of document size.
I have allocated 80GB of memory to Krita, and I swap undo after 25GB. Swap file
size limit is 64GB

If I restart Krita and re-open the document, the performance decrease remains,
so I'm not sure if it's an undo history problem. This doesn't seem to be true
with a full restart, or if Krita is off for a long enough time(?).

[ All comparisons are done on the same document, with the same number of
layers, after drawing for 4 hours vs restarting computer and opening the
document fresh. ]
'Performance decreases' include:
- Lower brush rendering speed (40fps vs 65 usual)
- Significant delay (110ms vs <16ms) after brush strokes end before the cursor
becomes responsive again
- Much slower hiding/unhiding of layers. (1-2 seconds vs 30-50ms)
- Layer transformation previewing and processing. Beginning a transformation
can take multiple seconds for a preview to load. Applying a transformation can
take several seconds vs less than a second.
- Undo/Redo gets a significant delay (unmeasured, but I can feel it)

I haven't noticed much else, but considering most of these make up 95% of my
time in front of Krita, it does become very noticeable.
Any advice for how to track the cause down on my end during my usual drawing
sessions, without negatively impacting my ability to work would be appreciated.

-----------------

System specs:

Windows 11 dev snapshot 22622
AMD 5800X hyperthreading disabled
128GB 3600mhz RAM
C: WD Black Gen4 NVME
Nvidia RTX 3090 21GB

Krita system info dump:

Krita
  Version: 5.2.0-prealpha (git d700876)

Qt
  Version (compiled): 5.12.12
  Version (loaded): 5.12.12

OS Information
  Build ABI: x86_64-little_endian-llp64
  Build CPU: x86_64
  CPU: x86_64
  Kernel Type: winnt
  Kernel Version: 10.0.22622
  Pretty Productname: Windows 10 (10.0)
  Product Type: windows
  Product Version: 10


OpenGL Info

  Vendor:  "Google Inc. (NVIDIA)" 
  Renderer:  "ANGLE (NVIDIA, NVIDIA GeForce RTX 3090 Direct3D11 vs_5_0 ps_5_0,
D3D11-30.0.15.1277)" 
  Version:  "OpenGL ES 3.0.0 (ANGLE 2.1.0 git hash:
f2280c0c5f93+krita_qt5.12.12)" 
  Shading language:  "OpenGL ES GLSL ES 3.00 (ANGLE 2.1.0 git hash:
f2280c0c5f93+krita_qt5.12.12)" 
  Requested format:  QSurfaceFormat(version 3.0, options
QFlags<QSurfaceFormat::FormatOption>(DeprecatedFunctions), depthBufferSize 24,
redBufferSize 8, greenBufferSize 8, blueBufferSize 8, alphaBufferSize 8,
stencilBufferSize 8, samples -1, swapBehavior QSurfaceFormat::DoubleBuffer,
swapInterval 0, colorSpace QSurfaceFormat::DefaultColorSpace, profile 
QSurfaceFormat::CompatibilityProfile) 
  Current format:  QSurfaceFormat(version 3.0, options
QFlags<QSurfaceFormat::FormatOption>(), depthBufferSize 24, redBufferSize 8,
greenBufferSize 8, blueBufferSize 8, alphaBufferSize 8, stencilBufferSize 8,
samples 0, swapBehavior QSurfaceFormat::DefaultSwapBehavior, swapInterval 0,
colorSpace QSurfaceFormat::DefaultColorSpace, profile 
QSurfaceFormat::NoProfile) 
     Version: 3.0
     Supports deprecated functions false 
     is OpenGL ES: true 
  supportsBufferMapping: true 
  supportsBufferInvalidation: false 
  forceDisableTextureBuffers: true

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to