High CPU load when using ASP

[Amamba]

I have tried to use ASP for the last month or so and I am getting really frustrated. A part of it has to do with the output I am getting, so I am writing it off to inexperience (I've only used Canon DPP Raw editor in the past, and it has several very useful presets custom-tailored to Canon CR2 RAWs).

The other problem, however, seems to be squarely related to ASP. I get very high CPU load while doing basic tasks, and overall it tends to be laggy and unresponsive, that really cuts into my processing time. I get the same problems with PSP, too. It seems Corel has a major issues with CPU loading in their programs. I run W7 x 64 machine with 2.7 MHz dual-core Pentium IV and 4 GB RAM, and had no problems with any other graphic processing software I've tried. I do load a few plugins (Bez, zPerspective) but I had this issue before I loaded them, too. It got to the point where for the last week I went back to using DPP and Gimp almost exclusively, and feel that my Corel products may end up on eBay.

I am curious if anyone else has similar issues.

[afx]

AS is coded to use a much CPU as it can get as it is optimized for multicore systems. It has a completely different Architecture than PSP.

I have no laggyness in basic AS neither on my dualcore Linux Laptops nor on my W7 64bit quadcore box. The only time I notice delays is when using Wavelet sharpen or NN which are both rather CPU intensive tools.

Are you working with AS while it is still generating previews? Then AS is dedicating some parts to background work which on older dualcore boxes can have quite an impact on the perceived foregorund performance.

cheers
afx

[claudermilk]

I'm running a 2.8GHZ hexa-core machine, and see that ASP utilizes all the processors. During normal editing, it's about 25-50% total usage. During batch output, it pegs the machine at 100%. I haven't used PSP much, but it seems a lot lighter on the CPU usage.

I've also upgrade recently to max the mobo at 16GB RAM, and rarely see that go above 3-5GB used.

I see little lag in the UI response, but there is some occasionally. Considering all the work it does for each screen refresh I'm not too surprised. I'm evaluating some other processors, and they take even longer to refresh the image.

[madsec]

I've also upgrade recently to max the mobo at 16GB RAM, and rarely see that go above 3-5GB used.

Since ASP is still 32bit it wouln't use more then 4 GB RAM ever.

[claudermilk]

Correct. I know there has been some noise about wishing for a 64-bit compile of ASP.

[HCS]

I've also upgrade recently to max the mobo at 16GB RAM, and rarely see that go above 3-5GB used.

Since ASP is still 32bit it wouln't use more then 4 GB RAM ever.

True, but the OS could (other programs, caching) or you could make a RAM drive for swapping. That would also increase speed. I have 48GB and don't have problems that often are rather vague, but in many cases caused by some memory shortage somewhere (not necessarily the app you're working in).