Re: [Gimp-user] Re: Cpu usage and speed - test results
On 27/02/2005, at 4:51 AM, GSR - FR wrote: [EMAIL PROTECTED] (2005-02-26 at 1805.22 +1100): In order to get past any background processing photoshop may have been doing, I also tried adjusting the curve in the curves dialog then quickly hit OK - this came out taking the same time as if I moved the curve and waited 10 seconds before clicking OK. Closing the image immediately afterwards was also instant, so there seemed to be no tricky background processing happening over the whole image area. For anybody trying to guess about background tricks, best would be a system monitor and see the CPU load. If app says it has ended, but the monitor reports the app is eating near 100%, there are some kind of trick there, or interface oriented optimization, it depends the point of view. So fire up top, gkrellm, activity monitor, task manager or whatever you have in the OS and see what is really going on. Aha! - That has revealed it I think - from the results it seems there may be background completion of each task, and perhaps some form of queuing as well. Doing one Levels change across the image in Photoshop came out as in my earlier post - with control coming back to me within a second - but top showed CPU use was above 70% for another 4 seconds before it dropped down to 1-2% idle again. Doing eight operations quickly, one after another - a combination of adjusting curves, levels and color balancing - left the cpu use peaking up high for about 16 seconds after finishing the last op. I'd expect to see that if each operation was being queued. Whatever it's doing in the background is transparent enough that zooming around and drawing over the image works OK as it's happening - prioritising what needs to be quick & interactive, and playing catchup with the rest a bit later whenever the user pauses. I imagine many of the benefits of an interface optimisation like that would be lost for heavily scripted processes involving those colour based functions ( levels, color balance, curves, brightness/contrast, posterize etc). dana -- http://www.danaquarium.com/ ___ Gimp-user mailing list Gimp-user@lists.xcf.berkeley.edu http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-user
[Gimp-user] Re: Cpu usage and speed - test results
Hi, [EMAIL PROTECTED] (2005-02-26 at 1805.22 +1100): > In order to get past any background processing photoshop may have been > doing, I also tried adjusting the curve in the curves dialog then > quickly hit OK - this came out taking the same time as if I moved the > curve and waited 10 seconds before clicking OK. Closing the image > immediately afterwards was also instant, so there seemed to be no > tricky background processing happening over the whole image area. For anybody trying to guess about background tricks, best would be a system monitor and see the CPU load. If app says it has ended, but the monitor reports the app is eating near 100%, there are some kind of trick there, or interface oriented optimization, it depends the point of view. So fire up top, gkrellm, activity monitor, task manager or whatever you have in the OS and see what is really going on. GSR ___ Gimp-user mailing list Gimp-user@lists.xcf.berkeley.edu http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-user
Re: [Gimp-user] Re: Cpu usage and speed
Sven Neumann wrote: Hi, Michele Petrazzo <[EMAIL PROTECTED]> writes: Did you use the default value for the tile cache size, or did you adjust it? The default value is 128 MB IIRC, but if you're going to open large images and you have 1 GB of RAM, it should be much higher than that. On linux machine I found only "maximum size of new image" Look again then; it's in the Environment preferences page. And GIMP did also explain this setting to you when it run the user installation. Opss! I found it. But on linux machine, this isn't the problem. The big problem on this OS, is the cpu time. I think that 70-80 sec for a preview of a command is too much, also if I work on a big image. So I think that gimp is not able to work with this big image. Thanks, Michele Petrazzo ___ Gimp-user mailing list Gimp-user@lists.xcf.berkeley.edu http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-user
Re: [Gimp-user] Re: Cpu usage and speed
Hi, Michele Petrazzo <[EMAIL PROTECTED]> writes: >> Did you use the default value for the tile cache size, or did you >> adjust it? The default value is 128 MB IIRC, but if you're going to >> open large images and you have 1 GB of RAM, it should be much >> higher than that. > > On linux machine I found only "maximum size of new image" Look again then; it's in the Environment preferences page. And GIMP did also explain this setting to you when it run the user installation. Sven ___ Gimp-user mailing list Gimp-user@lists.xcf.berkeley.edu http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-user
Re: [Gimp-user] Re: Cpu usage and speed
Roel Schroeven wrote: Michele Petrazzo wrote: hardware: cpu amd 2600+, 1GB ram, hd 80GB Maxtor, ati 7000 64MB Is this correctly, so gimp don't work well with these big image? Did you use the default value for the tile cache size, or did you adjust it? The default value is 128 MB IIRC, but if you're going to open large images and you have 1 GB of RAM, it should be much higher than that. On linux machine I found only "maximum size of new image", so if I set it to "n" MB, gimp not work better or worse than n +100 MB. On win machine, there are 3 or 4 parameters (I don't have gimp on win over my hands), and I remember that I try a lot differents setting, but the better result is that I wrote. I don't know what the optimal size is in your case, but I'd try with something like 768 MB, or even more if you're not planning to run a lot of other applications concurrently with Gimp. Of course, I have made this tries only with gimp open. Thanks, Michele Petrazzo Italy ___ Gimp-user mailing list Gimp-user@lists.xcf.berkeley.edu http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-user
[Gimp-user] Re: Cpu usage and speed
Michele Petrazzo wrote: > hardware: cpu amd 2600+, 1GB ram, hd 80GB Maxtor, ati 7000 64MB > Is this correctly, so gimp don't work well with these big image? Did you use the default value for the tile cache size, or did you adjust it? The default value is 128 MB IIRC, but if you're going to open large images and you have 1 GB of RAM, it should be much higher than that. I don't know what the optimal size is in your case, but I'd try with something like 768 MB, or even more if you're not planning to run a lot of other applications concurrently with Gimp. -- "Codito ergo sum" Roel Schroeven ___ Gimp-user mailing list Gimp-user@lists.xcf.berkeley.edu http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-user
