I've used PhotoImpact 6 for years. Recently I thought I should consider upgrading to 10. My trial version of 10, however, seems very resource hungry.
Specifically, it eats up 60% to 90% of CPU cycles continuously, whether I'm using it or just letting it stay open while using other apps. This definitely slows down overall system performance and is unacceptable.
I'm using Windows XP with a gig of RAM, P4 3GHz processor -- all recent, Dell equipment, lots of hard drive space.
What gives? Anyone else experience this kind of thing?
Thanks for any feedback.
Orson
Resource usage by PhotoImpact 10
-
2log
re: Resource usage by PhotoImpact 10
I only have 256MB of physical memory and the memory usage from Task Manager only averages about 15% average... that's with PhotoImpact 10 running with a lot of different programs like Internet Explorer, Microsoft Excel, Outlook, etc.
What OS are you using? You might want to reinstall the software and apply the patch as well. You can download the patch from the Ulead website (PhotoImpact section).
What OS are you using? You might want to reinstall the software and apply the patch as well. You can download the patch from the Ulead website (PhotoImpact section).
-
jimojimo
...10 is more resource efficient than XL...
I can tell you that v10 is much, much better at resource efficiency than my previous version, XL, though I can't speak for V8. In XL, my machine, with 1.5 gig RAM, would run through that and start hitting the swapfile after about 15 min or less of heavy usage.
Now in v10, it will gradually take memory up to about 800meg, but it seems to stay below the point where it starts hitting the pagefile, typically for at least 45 min. After that, it occasionally will climb past the physical mem limit if I'm still working with several large (30Meg jpg/100meg raw) files.
When it does, I just close PI and reopen, and I'm good to go. Bottom line--I can go for much longer before I have to close/reopen, and for that it was well worth the upgrade.
--Jim
Now in v10, it will gradually take memory up to about 800meg, but it seems to stay below the point where it starts hitting the pagefile, typically for at least 45 min. After that, it occasionally will climb past the physical mem limit if I'm still working with several large (30Meg jpg/100meg raw) files.
When it does, I just close PI and reopen, and I'm good to go. Bottom line--I can go for much longer before I have to close/reopen, and for that it was well worth the upgrade.
--Jim
