Xtreme Pro slow

**willdean** · 24 February 2010, 03:24 PM

Originally Posted by killerwhale65

ok, well not that i am a technician, but i think i can follow you.

It's a fair point that Xara have been caught-out in some assumption about multi-core behaviour which doesn't hold true for recent processors.

But I suspect that anyone hoping for Intel to fix this rather than Xara will be in for a long wait...

**killerwhale65** · 24 February 2010, 03:36 PM

my thoughts exactly. But shouldn't there be other software that suffers from this?

**willdean** · 24 February 2010, 03:41 PM

Originally Posted by killerwhale65

my thoughts exactly. But shouldn't there be other software that suffers from this?

There are an almost infinite number of ways to introduce multi-threading bugs into applications. It would appear that Xara found a way which most other people have overlooked ;-)

I don't know why it isn't fixed yet when it's been talked about for six months or so, but it's never easy to tell what's happening at Xara-towers from the outside.

**Soquili** · 24 February 2010, 04:10 PM

Other software is not written in low level machine code, which is the source of Xara's speed in a 32bit environment.

I do not work for Xara and cannot speak for them but to assume that a fix can be quickly accomplished is overlooking too many variables.

**killerwhale65** · 24 February 2010, 04:18 PM

ok, i see. Let's hope for the best. For the moment i am happy with the registry fix!

**willdean** · 24 February 2010, 04:23 PM

Originally Posted by Soquili

Other software is not written in low level machine code, which is the source of Xara's speed in a 32bit environment.

I do not work for Xara and cannot speak for them but to assume that a fix can be quickly accomplished is overlooking too many variables.

Lol. Sometimes I wonder if I only post here as a means of seeing what imaginative excuses the regulars can come up with when they detect something which might be taken as a slight against Xara.

Multithreaded code is very hard to get right regardless of the language you write your applications in. There's no great shame in having a latent bug exposed by subsequent hardware improvements.

But there is a legitimate question to be asked as to why, when X have known about this since at least last summer, they've not fixed it yet. Multithreaded rendering was only introduced recently, so it can hardly be said to be some ancient unmaintainable legacy feature.

**Soquili** · 24 February 2010, 04:42 PM

No one is trying to provide "imaginative" excuses. You posted about an issue and I simply provided an alternative work around. You can either use the registry change or turn off Hyper Threading. Your choice.

Neither you nor I know what steps Xara has been or is currently taking about this problem.

I simply find it amusing that people continue to post about an issue without reguard to what may be required to correct it or patience to wait for an update.

**graphicsfactory** · 26 February 2010, 03:08 PM

I also have this same problem, and contacted Xara support. They are aware and say they are working on it. But, I really encourage everyone having this problem, to contact support to provide feedback. That way they can have a more accurate gauge on the scope of the problem, and maybe identify some anomaly that can be fixed. This problem REALLY effects my work. I'm saddened by the fact that after spending thousands of dollars on a new computer and upgraded software, the performance of the one program that I use the most every day, actually got worse.

Thanks,
Mike