02-14-2023, 12:32 AM
Just to be abundantly clear, my machine has only one physical CPU, twin core, multi-threaded, and has always shown up as a 4 core machine on various diagnostics. I just wanted to clarify that, to eliminate any potential that might otherwise mislead you.
And frankly, I'm pleased to have the work load distributed across the "4 of them", rather than focused on one.
In fact, a source of irritation for me is the way Gimp uses the 4 cores when encoding a .webp animation. Look at the following, note you are looking at 5 screenshots taken at slightly later times (8:54, 8:58, 8:59:08, 8:59:44, and 9:00 PM) note the way the work is concentrated mostly on one core at any particular time, while the other three remain idle.My thought is that is very poor utilization.
All 5 screenshots were taken while creating a single .webp animation, on this same machine we are talking about here.
So clearly this Gimp and this OS do multi-threading
------------------------------------------------------------------------------------
Compare this to the way Kdenlive distributes it's work across the 4 cores,(following graphic) keeps them all 4 pretty loaded up (look closely at the top of each waveform, you'll notice that each is distinct from the others.
I'd think that was what one would hope for? A true essence of "distributed processing".
So, what tile cache setting would you recommend for me?
And is the Gimp "swap" entity something other than the swapper file used by the OS? Seems odd that Gimp claims to have used some, while Gkrel claims not. just curious.
And frankly, I'm pleased to have the work load distributed across the "4 of them", rather than focused on one.
In fact, a source of irritation for me is the way Gimp uses the 4 cores when encoding a .webp animation. Look at the following, note you are looking at 5 screenshots taken at slightly later times (8:54, 8:58, 8:59:08, 8:59:44, and 9:00 PM) note the way the work is concentrated mostly on one core at any particular time, while the other three remain idle.My thought is that is very poor utilization.
All 5 screenshots were taken while creating a single .webp animation, on this same machine we are talking about here.
So clearly this Gimp and this OS do multi-threading
------------------------------------------------------------------------------------
Compare this to the way Kdenlive distributes it's work across the 4 cores,(following graphic) keeps them all 4 pretty loaded up (look closely at the top of each waveform, you'll notice that each is distinct from the others.
I'd think that was what one would hope for? A true essence of "distributed processing".
So, what tile cache setting would you recommend for me?
And is the Gimp "swap" entity something other than the swapper file used by the OS? Seems odd that Gimp claims to have used some, while Gkrel claims not. just curious.