RE: Sql priority

scott:

what this setting does is tell the windows server to give any sql server threads a higher priority (thus more of a time slice from the processor) than other processes/threads.  so when sql server spawns threads for work, the threads will be configured with "setthreadpriority" set to 13 as the priority (HIGH_PRIORITY_CLASS and THREAD_PRIORITY_NORMAL ).  in this mode, the sql server thread will get more of a slice of processing time vs. other processes/threads.

since "most" of vault's work is executed within sql server, those portions will complete faster than normal (more time on the processor).  in the single user case, this doesn't really matter - the asp.net threads will blocking while sql server is running a query, and the sql server threads are idle when the asp.net code is running.  

the key is what happens when multiple threads of asp.net are running during multiple execution of sql server threads.  in this case, if the asp.net threads receive less processor time, then the asp.net code may be less responsive.  for example getting a list of file between two cached trees will be slower, but getting a list of checkouts will be faster.  like i mentioned in the last paragraph, most of the work vault executes requires some sql server interaction. 

fwiw, microsoft only recommends using this setting if the box is specifically dedicated for sql server.

hth
jeff
sourcegear


*********** REPLY SEPARATOR  ***********

On 2/20/2004 at 3:48 PM Eric Sink wrote:

>Prediction:
>
>SourceGear's Profiling Fanatic (Jeremy Sheeley) 
>will soon respond to this note and remind us all
>that the only way to really know how performance 
>will be affected by a change is to actually make 
>that change and then measure the difference.
>
>:-)
>
>--
>Eric Sink
>Software Craftsman
>http://software.ericsink.com/
>
> 
>-----Original Message-----
>From: [email protected]
>[mailto:[email protected]] On Behalf Of Scott LaFave
>Sent: Friday, February 20, 2004 1:20 PM
>To: SourceGear Vault MailList ([email protected])
>Subject: [vault-list] Sql priority
>
>If we have vault and sql on the same server (dedicated), does anyone have
>an
>opinion on boosting sql priority on the server?  I was thinking since sql
>is
>probably where most of the performance hit is on large operations, maybe it
>would make sense to favor it when the machine is busy.
>
> 
>
>Scott LaFave, MCSD
>
>Software Architect
>
>TReND
>
>660 American Avenue, Suite 203
>
>King of Prussia, PA 19406
>
>E-mail: [email protected]
>
>Phone: 610.783.4650 x177
>
>Fax: 610.783.4695
>
>Web: www.trendmls.com
>
> 
>
>
>_______________________________________________
>vault-list mailing list
>[email protected]
>http://lists.sourcegear.com/cgi-bin/mailman/listinfo/vault-list