LS60 = lots of memory!

[lozoyad]

Pekka,

I was wondering if there is a way to trim down the memory usage of LS 1.02...the beta version didn't appear to use nearly as much memory. Do the aftershave options have anything to do with this?Anyone with less that 1gig will have a slow go. On my machine (Athlon 2100) at 512meg it just isn't enough...its painfully slow, but once I added another 512meg it went along just fine.

Is it just me or are others experiencing similar behavior?

[rickm]

So adding THAT much memory did help? Wow, I thought at that point it was shear processor speed, not memory. Yep, it's slow on my P4-1400 w/512MB. Like they say though, good things come to those who wait...

[lozoyad]

Rickm,

Yep...I cut the time in half by going to 1gig. In PS 7.01 the LS60 action will use up to 700meg! I think that is just way out of whack. I could be wrong about this but it seems to shoot up when the aftershave options being established. You can watch it climb using the Task Manager. I can only process one image at a time, if I add another image to PS it just starts to virtualize the memory by hitting the disk...end result is a slower process.

I'm wondering if there is anything in PS we can do to help govern this. I realize that you can trim down the amount of memory PS uses...that's easy, right now I have it set to about 65%, but anything less and it slows down when using LS60. But I have noticed that the memory remains allocated to PS even after I close the image. Does anyone know how to flush this memory free without closing down PS?

[Morden]

So adding THAT much memory did help? Wow, I thought at that point it was shear processor speed, not memory.
I agree with the memory upgrade solution; I too went from 512 MB to 1 GB RAM and noticed a tremendous reduction in swapping, and therefore a massive reduction in the time it took LS D60 to work through a batch of image files.

And to think, my Sinclair ZX81 has only 1 K of RAM!

[lozoyad]

All,

...if only I would pay closer attention! Pekka knows what he is doing...I certainly don't with these actions. However, I did stumble unto a solution for those that have limited memory (under 512meg). The problem is that the LS_D60 action comes with the assumption that everyone has enough memory to run it. If you have 1 gig all is fine, but I bet many do not. Go into the aftershave action and do what its says (just tick one)...deselect all but one sub-action. I only selected (ticked) 'Brightness 0, Saturation 0'. Not only is is faster but the action does not use up all your memory.

The first sub-action in After Shave is the The 'chooser' action. Its a bit confusing...looks like its setting history snapshots...and this is where the extra memory is consumed. At any rate I decided not to use it at all.

[Pekka]

lozoyad has it right - if you don't need chooser check it off and use only one of the single snapshots.

Other way to improve speed is to set number of history points to 1.

I upgraded to PS 7 and they still have the same old bug: even if you close all windows RAM is not cleared. This means you get to "swap" mode really soon. Vey annoying and just tells how Adobe developers do not actually use their programs in real life.

I am gradually doing new sharpenings which are faster (and better) - I'm not interesting in waiting for results either so one main issue to improve is speed and memory usage.

[henkbos]

Hi all,

Tried the action the other day and was disappointed in the performance. Took hours to process about 50 shots on a 2.4Ghz, 1GB of memory, scratch disk definied on different disk AND different controller.
Can some1 provide a list of options that can be switched off during processing?

Good news remains that the result is better (for me) than with the FM actions.

Henk

[henkbos]

Did some timig and it takes 4:19 per picture. What can be wrong here?