Richard Alvarez
June 9th, 2004, 02:56 PM
Gang,
Recently had my system upgraded to dual xeons, and some aspects of Avid XpressPro are now sluggish. I see Avid reccomends turning OFF hyperthreading with dual xeons.
Can someone tell me how to accomplish this? (I know its "In my BIOS" but I need a bit more instruction.)
Thanks.
Mike Rehmus
June 9th, 2004, 10:42 PM
Xeons don't have HT, do they?
HT is managed by the BIOS so you need to enter BIOS setup at startup and turn off HT. That is assuming a dual Xeon MB has such a setting.
Richard Alvarez
June 10th, 2004, 07:28 AM
Yup, they have hyperthreading. THe dual Xeons show up as four processors in my task manager.
How does one "Enter the BIOS" at setup? I'm not particularly computer literate.
Mike Rehmus
June 10th, 2004, 12:05 PM
normally the first or second screen will have a text message that tells you which keyboard keys to push to enter the BIOS setup.
Most frequently that is the Del key.
George Ellis
June 10th, 2004, 12:51 PM
As Mike said, or it could be F2, F10, or F12 depending on the machine. It may say Press xxx to Enter Setup during the first boot screen. It will then be one of the opens in one of the areas in BIOS. It will not be on the first page that will show which usually has the time and date. Read the key descriptions from that point.
I wonder if Avid will fix their issue?
Richard Alvarez
June 10th, 2004, 06:04 PM
It's not an "issue" as they see it. They reccomend hyperthreading for singles, just not doubles. Other programs are much the same.
Thanks for the input, I'll see if it makes a difference.
Adrian Douglas
June 10th, 2004, 09:36 PM
Richard if you are not sure of what you are doing then I wouldn't recommend making BIOS changes. If you change the wrong thing you could affect something critical so you'd be better getting someone who knows what to do to do it for you.
Richard Alvarez
June 11th, 2004, 04:56 AM
Adrian,
I understand your concern, and feel exactly the same way. At this point, I am not certain its a hyperthreading issue. I am chasing down the possibility that it is a 'refresh' issue. So the Bios adventure is on hold.