Re: Worker Threads
- From: "Shane" <Shane@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Mon, 9 May 2005 09:11:15 -0700
Andrew,
Thanks for the reply.
All the settings you have mentioned are set in the boot.ini file. We do
have Advanced Server 2000 and Enterprise Server 2000 because of the
clustering.
One of the things I will do is set the maximum memory to 7Gb but when I say
the server is using 2.7Gb, I meant the SQL Server process in task manager.
How would I know if I am running out of worker threads? Do I look in event
viewer as it does for file servers?
Cheers
Shane
"Andrew J. Kelly" wrote:
> Shane,
>
> In order to use more than 4GB of memory you must use AWE. When you use AWE
> memory is no longer dynamic and SQL Server will grab everything up to the
> Max Memory limit for the memory pool and up to 384MB for MemToLeave. So I
> find it hard to believe you are only using 2.7GB unless you do not have the
> proper configurations. One is you must have Enterprise Edition of SQL
> Server and at least Advanced Server Win2000. Another is you must have PAE
> set in the Boot.ini and AWE enabled in SQL Server. The /3GB is optional with
> this amount of memory but it looks like you have it on. I suggest you
> double and triple check to ensure you have all of these correct as it does
> not appear to be so. And when you do get it set properly you should drop
> your max memory down to say 7.0 GB. A setting of 7.6GB with AWE will leave
> only ~400MB for MemToLeave and the OS. This is usually not enough to ensure
> proper operation under most conditions. Now as for the worker threads. Do
> you know for a fact you are running out of them? Just because you have 1200
> users does not mean you need that many worker threads. You actually require
> much less and how many depends on how they are being used etc. If you are
> not receiving errors stating you are out of worker threads I would leave it
> alone.
>
> --
> Andrew J. Kelly SQL MVP
>
>
> "Shane" <Shane@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> news:533AA171-63E1-4301-AC77-4D0FC1F543E8@xxxxxxxxxxxxxxxx
> > Hi,
> >
> > I'm having performance issues on my SQL2000 box.
> >
> > We currently have a clustered Windows 2000 Microsoft SQL 2000 server. The
> > node contains 8 processors and 8GB RAM. I have limited the SQL server to
> > use
> > 7.6Gb but is only currently using 2.7Gb.
> >
> > Current connections to the SQL box is between 1100 and 1200 and may
> > decrease
> > but not necessarily increase.
> >
> > The worker threads are still at the default of 255. I want to change it
> > to
> > 1000 but the articles from Microsoft do not give me much confidence.
> >
> > Has anybody else done any changes like this before and if so, what were
> > the
> > effects of this change.
> >
> > Any help would be greatly appreciated so that I don't make preformance
> > worse
> > than it already is.
> >
> > Cheers
> >
> > Shane
>
>
>
.
- Follow-Ups:
- Re: Worker Threads
- From: Andrew J. Kelly
- Re: Worker Threads
- References:
- Worker Threads
- From: Shane
- Re: Worker Threads
- From: Andrew J. Kelly
- Worker Threads
- Prev by Date: SQL Server Service doesn't start
- Next by Date: Re: Worker Threads
- Previous by thread: Re: Worker Threads
- Next by thread: Re: Worker Threads
- Index(es):
Relevant Pages
|
