On Oct 1, 2005, at 10:37 AM, JC Car wrote:

Not sure if I asked that in correct terms, but in my Adobes I am able to assign memory usage and scratch disks. I am enjoying Inkscape tremendously and REALLY would like to use it more in my work (I am an illustrator). But it runs very slow and take a while to refresh the display when any changes are made or a new work window is opened.

There's nothing that specific in Inkscape.

Much of that in the Adobe products is legacy from when Apple's early OS didn't support virtual memory well, had to allocate each program it's full possible block at program launch, etc.

And when they started porting things over to Windows (which had better virtual memory support at the time, etc), they in essence just ported over huge chunks of MacOS code and replacements, including their own virtual memory subsystem.

I also have Inkscape installed in Ubuntu on another throw-together system, it seems to work a little smoother there, but still pretty slow.

That might just be due to Linux working more efficiently in that regard.

Some of the others here might point out things to do to help profile the performance and memory work (I haven't looked into those lately), but I just wanted to point out the outdated "why" of Adobe's "features".