MenTaLguY wrote:
On Fri, 2004-09-17 at 02:15, Jon Phillips wrote:
I tried it with a 1024 by 768 72 dpi jpg image...nothing fancy...and it brought it to its knees.
It seems fairly slow to me as well -- perhaps there is a more efficient way to use potrace than we are currently doing?
I tried with Jon's image and the standalone potrace, and it always finished in under 1 second. There must be something wrong with how it's integrated in inkscape.
One thing is that I use -O3, whereas you probably use -O2. One should manually inline a lot of functions in this case, to make it faster. This makes a difference of 20-30 percent. But this cannot be the only reason it is so slow. I compiled the standalone potrace with g++ and -O0 just for comparison, and it still finishes Jon's image in 1.5 seconds.
Could it be that it's actually the "canny" edge detection which is slow?
-- Peter