[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [krita] [Bug 393716] New: Setting 'Frame Rendering Clones Limit' does not seem to help with animatio
From:       <bugzilla_noreply () kde ! org>
Date:       2018-05-01 6:26:16
Message-ID: bug-393716-17878 () http ! bugs ! kde ! org/
[Download RAW message or body]

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

            Bug ID: 393716
           Summary: Setting 'Frame Rendering Clones Limit' does not seem
                    to help with animation
           Product: krita
           Version: 4.0.1
          Platform: MS Windows
                OS: MS Windows
            Status: UNCONFIRMED
          Severity: normal
          Priority: NOR
         Component: Animation
          Assignee: krita-bugs-null@kde.org
          Reporter: phaineofcatz@gmail.com
  Target Milestone: ---

Computer : Microsoft surface book with performance base
OS : windows 10
File : 900x666 three layers with 14 frames each and one layer without
animation(Attatched)

-Expected behavior
It is noted in documentation that with 'heavy' animations and multiple cores
you may experience slowdowns. The setting "Frame Rendering Clones Limit" is
supposed to let you work around this by basically limiting multi-threading for
animation only. 

-Actual Behavior
Thing is, this doesn't seem to do anything. Set to 4 works the same as set to
1. To actually limit things (and keep the app from freezing every few
brushstrokes in my case) you have to limit the whole application to only use a
set number of cores, which slows down other usages of multi-threading(most of
which have been working beautifully for me btw, thanks). 

It should also be noted that this is a full stop when it happens. Was set up
for using all four cores with zero slowdown, then I broke a certain threshold(I
presume memory usage) and every two or three brush strokes krita stops for a
full 15 count. It doesn't matter the size or complexity of the strokes, it is
the quantity. After this point I had to bring it down to one core to get any
sort of progress. I tried changing several other settings to do with memory
allocated to no avail. After setting the app to only use 1 core brush strokes
work as expected.

-Optimistic Future
It would be nice if this setting worked, since the only multi-threading issues
I have had have been with animation. Alternatively, if I am misunderstanding
the purpose of this setting, it would be nice to have a way to turn off
multi-threading just for animation frame clones.

-- 
You are receiving this mail because:
You are watching all bug changes.=
[prev in list] [next in list] [prev in thread] [next in thread]