Extended stored procedure performance tuning

We have an application that is based on several extended stored
procedures. When we run our application in house, or when most other
customers run it, they see performance of about X transactions per
second. One customer is seeing performance of about X/5, and I'm
having a hard time troubleshooting it. The performace bottleneck has
been narrowed to the execution of the extended stored procedures. Does
anyone know of tuneable SQL Server parameters that may specifically
affect the performance of extended stored procedures. I know the
procedures get run by a scheduler. Is there some way the priority or
frequency of the scheduler can be modified? Thanks for any advice.Are there lots of concurrent users in this one customer? This KB article
might be interesting
to you:

http://support.microsoft.com/?kbid=836839

--
Wei Xiao [MSFT]
SQL Server Storage Engine Development
http://blogs.msdn.com/weix

<bsandell@.gmail.com> wrote in message
news:1116439417.870512.217270@.g14g2000cwa.googlegr oups.com...
> We have an application that is based on several extended stored
> procedures. When we run our application in house, or when most other
> customers run it, they see performance of about X transactions per
> second. One customer is seeing performance of about X/5, and I'm
> having a hard time troubleshooting it. The performace bottleneck has
> been narrowed to the execution of the extended stored procedures. Does
> anyone know of tuneable SQL Server parameters that may specifically
> affect the performance of extended stored procedures. I know the
> procedures get run by a scheduler. Is there some way the priority or
> frequency of the scheduler can be modified? Thanks for any advice.|||Are you using synchronization objects inside the XP?
Loopback connections?

GertD@.SQLDev.Net

Please reply only to the newsgroups.
This posting is provided "AS IS" with no warranties, and confers no rights.
You assume all risk for your use.
Copyright SQLDev.Net 1991-2005 All rights reserved.

<bsandell@.gmail.com> wrote in message
news:1116439417.870512.217270@.g14g2000cwa.googlegr oups.com...
> We have an application that is based on several extended stored
> procedures. When we run our application in house, or when most other
> customers run it, they see performance of about X transactions per
> second. One customer is seeing performance of about X/5, and I'm
> having a hard time troubleshooting it. The performace bottleneck has
> been narrowed to the execution of the extended stored procedures. Does
> anyone know of tuneable SQL Server parameters that may specifically
> affect the performance of extended stored procedures. I know the
> procedures get run by a scheduler. Is there some way the priority or
> frequency of the scheduler can be modified? Thanks for any advice.|||Also check if you customer is running fibers or threads? exec sp_configure
'lightweight pooling'
Verify size of the MemToLeave area, maybe your customers runs with /3GB on
or off, of uses the -g startup parameter to set the MemToLeave area size in
SQL Server

GertD@.SQLDev.Net

Please reply only to the newsgroups.
This posting is provided "AS IS" with no warranties, and confers no rights.
You assume all risk for your use.
Copyright SQLDev.Net 1991-2005 All rights reserved.

"Gert E.R. Drapers" <gertdATsqldevDOTnet> wrote in message
news:428c7663$0$64595$e4fe514c@.news.xs4all.nl...
> Are you using synchronization objects inside the XP?
> Loopback connections?
> GertD@.SQLDev.Net
> Please reply only to the newsgroups.
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> You assume all risk for your use.
> Copyright SQLDev.Net 1991-2005 All rights reserved.
> <bsandell@.gmail.com> wrote in message
> news:1116439417.870512.217270@.g14g2000cwa.googlegr oups.com...
>> We have an application that is based on several extended stored
>> procedures. When we run our application in house, or when most other
>> customers run it, they see performance of about X transactions per
>> second. One customer is seeing performance of about X/5, and I'm
>> having a hard time troubleshooting it. The performace bottleneck has
>> been narrowed to the execution of the extended stored procedures. Does
>> anyone know of tuneable SQL Server parameters that may specifically
>> affect the performance of extended stored procedures. I know the
>> procedures get run by a scheduler. Is there some way the priority or
>> frequency of the scheduler can be modified? Thanks for any advice.
>>sql