August 14, 2009 at 12:25 pm
We have a variety of packages where DTExec (and therefore SSIS) are doing a fair amount of heavy lifting. When these are running, almost all the time the CPU utilization on the server will only be 13% (1 core maxed on 8 core machine). Since this machine is basically an SSIS machine, it seems like a waste. Unfortunately I haven't seen anything anywhere about making DTExec use more CPUs.
Windows Server 2003 Enterprise Edition x64
SQL Server 2005 Developer Edition x64
Thanks,
Rick Todd
August 14, 2009 at 12:41 pm
That is x86 so it is only seeing 32bits memory allocation and may be using just enough because in WOW64 it cannot use all your x64 available memory. I am not sure about the 1CPU but to use all 8 I think it must be configured in x86 opearting system.
Kind regards,
Gift Peddie
August 14, 2009 at 12:53 pm
Interesting, I just checked on my x64 development server and there is an x64 version of DTExec and an x86 version of DTExec on the system.
August 14, 2009 at 12:54 pm
Well, this is the 64bit DTExec (as opposed to the DTExec that's in the Program Files (x86) folder).
As for the rest of what you're saying I'm not sure how to look into any of this. Could you please expand upon your answer?
Rick Todd
August 14, 2009 at 1:00 pm
Not sure what is going on with your system either. i just started up a job on my system that has multiple data flow tasks running in parallel, and all 8 cores on my system are busy.
Are your SSIS packages being run serially?
August 14, 2009 at 1:11 pm
Win2003 comes with Non-Uniform Memory Access (NUMA) and other software based optimization tools but I find Win2003 SP2 fixed many problems with the operating system, I am not saying it is related to your problem.
Kind regards,
Gift Peddie
August 14, 2009 at 1:11 pm
Yes, it's serial because this section of our ETL can only be run serially. So I'd like it to take up more processors, if possible.
Rick Todd
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply