asp.net app outofmemory

I have a web application written using asp.net 2.0 and c#. Before it worked
on Windows Server 2000 and SQL Server 2000, but recently new server was
bought (to facilitate migration to sql2k5), and on it is windows server 2k3
r2 and sql server 2k5.
The app and the database is the same but now i frequently get outofmemory
exceptions, and from what i can see, w3wp process keeps requiring use of more
memory. SQL server takes 1.2gb in memory (thats what the task manager says)
and w3wp starts at 200-300mb and climbes up to 1.2g in memory before
outofmemory exception and then only iis reset helps.
pls help :)

Re: asp.net app outofmemory

object.dispose() :)

i would assume your code is leaving objects open and the garbage collector
cant keep up, that is to say, it cant touch it for 20 min until the session
ends...

if you cant clean up the code you can modify the session timeout periods and
other cache related properties (there is some DB caching you can control if
its a DB app)

i'd try to clean up the code if you can.

Justin



"Nedim" wrote in message
news:85527EB3-4BA9-4ED5-99A4-7BE8F72F98A6@microsoft.com...
>I have a web application written using asp.net 2.0 and c#. Before it worked
> on Windows Server 2000 and SQL Server 2000, but recently new server was
> bought (to facilitate migration to sql2k5), and on it is windows server
> 2k3
> r2 and sql server 2k5.
> The app and the database is the same but now i frequently get outofmemory
> exceptions, and from what i can see, w3wp process keeps requiring use of
> more
> memory. SQL server takes 1.2gb in memory (thats what the task manager
> says)
> and w3wp starts at 200-300mb and climbes up to 1.2g in memory before
> outofmemory exception and then only iis reset helps.
> pls help :)

Re: asp.net app outofmemory

It is a database app, but i do generally call dispose methods (maybe not in
all the places, I will check it and dispore more often), but it seems to grow
too rapidly to be just a .dispose problem.
how and where do i modify the session time out periods and db caching (i'm a
rookie administrator, that is, i have no idea what to do after i make a
virtual directory :))

"Justin Rich" wrote:

> object.dispose() :)
>
> i would assume your code is leaving objects open and the garbage collector
> cant keep up, that is to say, it cant touch it for 20 min until the session
> ends...
>
> if you cant clean up the code you can modify the session timeout periods and
> other cache related properties (there is some DB caching you can control if
> its a DB app)
>
> i'd try to clean up the code if you can.
>
> Justin
>
>
>
> "Nedim" wrote in message
> news:85527EB3-4BA9-4ED5-99A4-7BE8F72F98A6@microsoft.com...
> >I have a web application written using asp.net 2.0 and c#. Before it worked
> > on Windows Server 2000 and SQL Server 2000, but recently new server was
> > bought (to facilitate migration to sql2k5), and on it is windows server
> > 2k3
> > r2 and sql server 2k5.
> > The app and the database is the same but now i frequently get outofmemory
> > exceptions, and from what i can see, w3wp process keeps requiring use of
> > more
> > memory. SQL server takes 1.2gb in memory (thats what the task manager
> > says)
> > and w3wp starts at 200-300mb and climbes up to 1.2g in memory before
> > outofmemory exception and then only iis reset helps.
> > pls help :)
>
>
>

Re: asp.net app outofmemory

And, I never had a problem like that on Windows 2000 with the old IIS 5, I
get OutOfMemory exceptions on Win2k3 with IIS 6.


"Justin Rich" wrote:

> object.dispose() :)
>
> i would assume your code is leaving objects open and the garbage collector
> cant keep up, that is to say, it cant touch it for 20 min until the session
> ends...
>
> if you cant clean up the code you can modify the session timeout periods and
> other cache related properties (there is some DB caching you can control if
> its a DB app)
>
> i'd try to clean up the code if you can.
>
> Justin
>
>
>
> "Nedim" wrote in message
> news:85527EB3-4BA9-4ED5-99A4-7BE8F72F98A6@microsoft.com...
> >I have a web application written using asp.net 2.0 and c#. Before it worked
> > on Windows Server 2000 and SQL Server 2000, but recently new server was
> > bought (to facilitate migration to sql2k5), and on it is windows server
> > 2k3
> > r2 and sql server 2k5.
> > The app and the database is the same but now i frequently get outofmemory
> > exceptions, and from what i can see, w3wp process keeps requiring use of
> > more
> > memory. SQL server takes 1.2gb in memory (thats what the task manager
> > says)
> > and w3wp starts at 200-300mb and climbes up to 1.2g in memory before
> > outofmemory exception and then only iis reset helps.
> > pls help :)
>
>
>

Re: asp.net app outofmemory

yeah, there is a chance there might be something else wrong here, simple
because it worked ok in 2k and now in 2k3 you have problems.

Typically what you'll see in this case is that both SQL and IIS have a copy
resident in memory (same data in memory twice) and so you want to tell one
of these two systems not to do so much caching. the problem here is although
you can control how much cache they eat, you cant control them wanting to
eat it... and by that i mean, lets say you limit SQL to 500MB of memory, all
fine and dandy but the problem is SQL will still attempt to cache as much as
it can, basically wants to hold all the data it can, and if you tell it to
hold less, its still going to want to have the same data available to it, so
it ends up paging a lot (no longer a memory issue, now its a disk issue) so
although you can control the SQL memory usage, its not really that great of
an idea..

you can do it with in IIS i believe but off hand i dont know, id have to
look around for that one... but, basically its the same deal, IIS wants the
same amount of data... paging again...

based on the numbers you have tossed up here im going to assume you probably
only have 2GB of memory.. your best bet would be to toss another 2gb in this
system (2k3 standard can only use 4gb total) and you would probably be way
better off...


the next, and probably best way to do this, is to do this via code. SQL05
has some advanced cache management... but... thats all i know.. you can code
it different, its cool, and it helps.... sorry, only so much time to learn
:)


so, buy more memory if you can, otherwise limit the memory usage. you can
tell SQL to use less if you want, which can be done in SSMS via the
properties of the DB itself.. its in the obvious section of the properties,
memory, go figure :)


good luck

Justin

"Nedim" wrote in message
news:4BC2FC44-0DDD-4688-BF2A-2DBCAB8A1A77@microsoft.com...
> It is a database app, but i do generally call dispose methods (maybe not
> in
> all the places, I will check it and dispore more often), but it seems to
> grow
> too rapidly to be just a .dispose problem.
> how and where do i modify the session time out periods and db caching (i'm
> a
> rookie administrator, that is, i have no idea what to do after i make a
> virtual directory :))
>
> "Justin Rich" wrote:
>
>> object.dispose() :)
>>
>> i would assume your code is leaving objects open and the garbage
>> collector
>> cant keep up, that is to say, it cant touch it for 20 min until the
>> session
>> ends...
>>
>> if you cant clean up the code you can modify the session timeout periods
>> and
>> other cache related properties (there is some DB caching you can control
>> if
>> its a DB app)
>>
>> i'd try to clean up the code if you can.
>>
>> Justin
>>
>>
>>
>> "Nedim" wrote in message
>> news:85527EB3-4BA9-4ED5-99A4-7BE8F72F98A6@microsoft.com...
>> >I have a web application written using asp.net 2.0 and c#. Before it
>> >worked
>> > on Windows Server 2000 and SQL Server 2000, but recently new server was
>> > bought (to facilitate migration to sql2k5), and on it is windows server
>> > 2k3
>> > r2 and sql server 2k5.
>> > The app and the database is the same but now i frequently get
>> > outofmemory
>> > exceptions, and from what i can see, w3wp process keeps requiring use
>> > of
>> > more
>> > memory. SQL server takes 1.2gb in memory (thats what the task manager
>> > says)
>> > and w3wp starts at 200-300mb and climbes up to 1.2g in memory before
>> > outofmemory exception and then only iis reset helps.
>> > pls help :)
>>
>>
>>

Re: asp.net app outofmemory

Both servers have 4gb of ram (well the latter has 8g but we havent installed
64bit windows on it yet). will try puting a lot more .dispose in the hopes of
it helping.
but i observed the web server process today and it just kept taking more and
more memory, never releasing it (it takes 3mb when i log onto a web app, and
takes more as i work thru it, but when i close the browser and 20 min -
session expiry time - passes, it still keeps on taking more and more memory,
the amount of memory never goes down)

"Justin Rich" wrote:

> yeah, there is a chance there might be something else wrong here, simple
> because it worked ok in 2k and now in 2k3 you have problems.
>
> Typically what you'll see in this case is that both SQL and IIS have a copy
> resident in memory (same data in memory twice) and so you want to tell one
> of these two systems not to do so much caching. the problem here is although
> you can control how much cache they eat, you cant control them wanting to
> eat it... and by that i mean, lets say you limit SQL to 500MB of memory, all
> fine and dandy but the problem is SQL will still attempt to cache as much as
> it can, basically wants to hold all the data it can, and if you tell it to
> hold less, its still going to want to have the same data available to it, so
> it ends up paging a lot (no longer a memory issue, now its a disk issue) so
> although you can control the SQL memory usage, its not really that great of
> an idea..
>
> you can do it with in IIS i believe but off hand i dont know, id have to
> look around for that one... but, basically its the same deal, IIS wants the
> same amount of data... paging again...
>
> based on the numbers you have tossed up here im going to assume you probably
> only have 2GB of memory.. your best bet would be to toss another 2gb in this
> system (2k3 standard can only use 4gb total) and you would probably be way
> better off...
>
>
> the next, and probably best way to do this, is to do this via code. SQL05
> has some advanced cache management... but... thats all i know.. you can code
> it different, its cool, and it helps.... sorry, only so much time to learn
> :)
>
>
> so, buy more memory if you can, otherwise limit the memory usage. you can
> tell SQL to use less if you want, which can be done in SSMS via the
> properties of the DB itself.. its in the obvious section of the properties,
> memory, go figure :)
>
>
> good luck
>
> Justin
>
> "Nedim" wrote in message
> news:4BC2FC44-0DDD-4688-BF2A-2DBCAB8A1A77@microsoft.com...
> > It is a database app, but i do generally call dispose methods (maybe not
> > in
> > all the places, I will check it and dispore more often), but it seems to
> > grow
> > too rapidly to be just a .dispose problem.
> > how and where do i modify the session time out periods and db caching (i'm
> > a
> > rookie administrator, that is, i have no idea what to do after i make a
> > virtual directory :))
> >
> > "Justin Rich" wrote:
> >
> >> object.dispose() :)
> >>
> >> i would assume your code is leaving objects open and the garbage
> >> collector
> >> cant keep up, that is to say, it cant touch it for 20 min until the
> >> session
> >> ends...
> >>
> >> if you cant clean up the code you can modify the session timeout periods
> >> and
> >> other cache related properties (there is some DB caching you can control
> >> if
> >> its a DB app)
> >>
> >> i'd try to clean up the code if you can.
> >>
> >> Justin
> >>
> >>
> >>
> >> "Nedim" wrote in message
> >> news:85527EB3-4BA9-4ED5-99A4-7BE8F72F98A6@microsoft.com...
> >> >I have a web application written using asp.net 2.0 and c#. Before it
> >> >worked
> >> > on Windows Server 2000 and SQL Server 2000, but recently new server was
> >> > bought (to facilitate migration to sql2k5), and on it is windows server
> >> > 2k3
> >> > r2 and sql server 2k5.
> >> > The app and the database is the same but now i frequently get
> >> > outofmemory
> >> > exceptions, and from what i can see, w3wp process keeps requiring use
> >> > of
> >> > more
> >> > memory. SQL server takes 1.2gb in memory (thats what the task manager
> >> > says)
> >> > and w3wp starts at 200-300mb and climbes up to 1.2g in memory before
> >> > outofmemory exception and then only iis reset helps.
> >> > pls help :)
> >>
> >>
> >>
>
>
>

Re: asp.net app outofmemory

wait, how is this setup? two servers? does that mean you have IIS on one box
and SQL on the other?

why don't you explain how this is setup. which apps are where and which has
what memory... you might need to approach this differently..

Justin

"Nedim" wrote in message
news:079F544B-5CDF-4C97-9B9A-F1C33DFA44A2@microsoft.com...
> Both servers have 4gb of ram (well the latter has 8g but we havent
> installed
> 64bit windows on it yet). will try puting a lot more .dispose in the hopes
> of
> it helping.
> but i observed the web server process today and it just kept taking more
> and
> more memory, never releasing it (it takes 3mb when i log onto a web app,
> and
> takes more as i work thru it, but when i close the browser and 20 min -
> session expiry time - passes, it still keeps on taking more and more
> memory,
> the amount of memory never goes down)
>
> "Justin Rich" wrote:
>
>> yeah, there is a chance there might be something else wrong here, simple
>> because it worked ok in 2k and now in 2k3 you have problems.
>>
>> Typically what you'll see in this case is that both SQL and IIS have a
>> copy
>> resident in memory (same data in memory twice) and so you want to tell
>> one
>> of these two systems not to do so much caching. the problem here is
>> although
>> you can control how much cache they eat, you cant control them wanting to
>> eat it... and by that i mean, lets say you limit SQL to 500MB of memory,
>> all
>> fine and dandy but the problem is SQL will still attempt to cache as much
>> as
>> it can, basically wants to hold all the data it can, and if you tell it
>> to
>> hold less, its still going to want to have the same data available to it,
>> so
>> it ends up paging a lot (no longer a memory issue, now its a disk issue)
>> so
>> although you can control the SQL memory usage, its not really that great
>> of
>> an idea..
>>
>> you can do it with in IIS i believe but off hand i dont know, id have to
>> look around for that one... but, basically its the same deal, IIS wants
>> the
>> same amount of data... paging again...
>>
>> based on the numbers you have tossed up here im going to assume you
>> probably
>> only have 2GB of memory.. your best bet would be to toss another 2gb in
>> this
>> system (2k3 standard can only use 4gb total) and you would probably be
>> way
>> better off...
>>
>>
>> the next, and probably best way to do this, is to do this via code. SQL05
>> has some advanced cache management... but... thats all i know.. you can
>> code
>> it different, its cool, and it helps.... sorry, only so much time to
>> learn
>> :)
>>
>>
>> so, buy more memory if you can, otherwise limit the memory usage. you can
>> tell SQL to use less if you want, which can be done in SSMS via the
>> properties of the DB itself.. its in the obvious section of the
>> properties,
>> memory, go figure :)
>>
>>
>> good luck
>>
>> Justin
>>
>> "Nedim" wrote in message
>> news:4BC2FC44-0DDD-4688-BF2A-2DBCAB8A1A77@microsoft.com...
>> > It is a database app, but i do generally call dispose methods (maybe
>> > not
>> > in
>> > all the places, I will check it and dispore more often), but it seems
>> > to
>> > grow
>> > too rapidly to be just a .dispose problem.
>> > how and where do i modify the session time out periods and db caching
>> > (i'm
>> > a
>> > rookie administrator, that is, i have no idea what to do after i make a
>> > virtual directory :))
>> >
>> > "Justin Rich" wrote:
>> >
>> >> object.dispose() :)
>> >>
>> >> i would assume your code is leaving objects open and the garbage
>> >> collector
>> >> cant keep up, that is to say, it cant touch it for 20 min until the
>> >> session
>> >> ends...
>> >>
>> >> if you cant clean up the code you can modify the session timeout
>> >> periods
>> >> and
>> >> other cache related properties (there is some DB caching you can
>> >> control
>> >> if
>> >> its a DB app)
>> >>
>> >> i'd try to clean up the code if you can.
>> >>
>> >> Justin
>> >>
>> >>
>> >>
>> >> "Nedim" wrote in message
>> >> news:85527EB3-4BA9-4ED5-99A4-7BE8F72F98A6@microsoft.com...
>> >> >I have a web application written using asp.net 2.0 and c#. Before it
>> >> >worked
>> >> > on Windows Server 2000 and SQL Server 2000, but recently new server
>> >> > was
>> >> > bought (to facilitate migration to sql2k5), and on it is windows
>> >> > server
>> >> > 2k3
>> >> > r2 and sql server 2k5.
>> >> > The app and the database is the same but now i frequently get
>> >> > outofmemory
>> >> > exceptions, and from what i can see, w3wp process keeps requiring
>> >> > use
>> >> > of
>> >> > more
>> >> > memory. SQL server takes 1.2gb in memory (thats what the task
>> >> > manager
>> >> > says)
>> >> > and w3wp starts at 200-300mb and climbes up to 1.2g in memory before
>> >> > outofmemory exception and then only iis reset helps.
>> >> > pls help :)
>> >>
>> >>
>> >>
>>
>>
>>

Re: asp.net app outofmemory

no, it was the old and the new server.
the old was an ibm p4 machine with 4gb of memory and windows 2000 server.
new is the dell with quad core xeon, 8gb of ram and a few disks with windows
2k3(so basically a beast of a server).
in the meantime we tried on the old sevrer again, but i get memory errors
again, so i guess we can rule that out.
the app is a basic database app. because the database is huge we try to
cache as much as possible so when the application starts, some smaller tables
that are always needed are put in the Application object, and when a user
logs in we put most tables in session object (basically one dataset with a
subset of results that are being shown to the user). Now I dont know how I
can clear that out of memory - I dont have a webpage_closed event in which i
could clear the tables

"Justin Rich" wrote:

> wait, how is this setup? two servers? does that mean you have IIS on one box
> and SQL on the other?
>
> why don't you explain how this is setup. which apps are where and which has
> what memory... you might need to approach this differently..
>
> Justin
>
> "Nedim" wrote in message
> news:079F544B-5CDF-4C97-9B9A-F1C33DFA44A2@microsoft.com...
> > Both servers have 4gb of ram (well the latter has 8g but we havent
> > installed
> > 64bit windows on it yet). will try puting a lot more .dispose in the hopes
> > of
> > it helping.
> > but i observed the web server process today and it just kept taking more
> > and
> > more memory, never releasing it (it takes 3mb when i log onto a web app,
> > and
> > takes more as i work thru it, but when i close the browser and 20 min -
> > session expiry time - passes, it still keeps on taking more and more
> > memory,
> > the amount of memory never goes down)
> >
> > "Justin Rich" wrote:
> >
> >> yeah, there is a chance there might be something else wrong here, simple
> >> because it worked ok in 2k and now in 2k3 you have problems.
> >>
> >> Typically what you'll see in this case is that both SQL and IIS have a
> >> copy
> >> resident in memory (same data in memory twice) and so you want to tell
> >> one
> >> of these two systems not to do so much caching. the problem here is
> >> although
> >> you can control how much cache they eat, you cant control them wanting to
> >> eat it... and by that i mean, lets say you limit SQL to 500MB of memory,
> >> all
> >> fine and dandy but the problem is SQL will still attempt to cache as much
> >> as
> >> it can, basically wants to hold all the data it can, and if you tell it
> >> to
> >> hold less, its still going to want to have the same data available to it,
> >> so
> >> it ends up paging a lot (no longer a memory issue, now its a disk issue)
> >> so
> >> although you can control the SQL memory usage, its not really that great
> >> of
> >> an idea..
> >>
> >> you can do it with in IIS i believe but off hand i dont know, id have to
> >> look around for that one... but, basically its the same deal, IIS wants
> >> the
> >> same amount of data... paging again...
> >>
> >> based on the numbers you have tossed up here im going to assume you
> >> probably
> >> only have 2GB of memory.. your best bet would be to toss another 2gb in
> >> this
> >> system (2k3 standard can only use 4gb total) and you would probably be
> >> way
> >> better off...
> >>
> >>
> >> the next, and probably best way to do this, is to do this via code. SQL05
> >> has some advanced cache management... but... thats all i know.. you can
> >> code
> >> it different, its cool, and it helps.... sorry, only so much time to
> >> learn
> >> :)
> >>
> >>
> >> so, buy more memory if you can, otherwise limit the memory usage. you can
> >> tell SQL to use less if you want, which can be done in SSMS via the
> >> properties of the DB itself.. its in the obvious section of the
> >> properties,
> >> memory, go figure :)
> >>
> >>
> >> good luck
> >>
> >> Justin
> >>
> >> "Nedim" wrote in message
> >> news:4BC2FC44-0DDD-4688-BF2A-2DBCAB8A1A77@microsoft.com...
> >> > It is a database app, but i do generally call dispose methods (maybe
> >> > not
> >> > in
> >> > all the places, I will check it and dispore more often), but it seems
> >> > to
> >> > grow
> >> > too rapidly to be just a .dispose problem.
> >> > how and where do i modify the session time out periods and db caching
> >> > (i'm
> >> > a
> >> > rookie administrator, that is, i have no idea what to do after i make a
> >> > virtual directory :))
> >> >
> >> > "Justin Rich" wrote:
> >> >
> >> >> object.dispose() :)
> >> >>
> >> >> i would assume your code is leaving objects open and the garbage
> >> >> collector
> >> >> cant keep up, that is to say, it cant touch it for 20 min until the
> >> >> session
> >> >> ends...
> >> >>
> >> >> if you cant clean up the code you can modify the session timeout
> >> >> periods
> >> >> and
> >> >> other cache related properties (there is some DB caching you can
> >> >> control
> >> >> if
> >> >> its a DB app)
> >> >>
> >> >> i'd try to clean up the code if you can.
> >> >>
> >> >> Justin
> >> >>
> >> >>
> >> >>
> >> >> "Nedim" wrote in message
> >> >> news:85527EB3-4BA9-4ED5-99A4-7BE8F72F98A6@microsoft.com...
> >> >> >I have a web application written using asp.net 2.0 and c#. Before it
> >> >> >worked
> >> >> > on Windows Server 2000 and SQL Server 2000, but recently new server
> >> >> > was
> >> >> > bought (to facilitate migration to sql2k5), and on it is windows
> >> >> > server
> >> >> > 2k3
> >> >> > r2 and sql server 2k5.
> >> >> > The app and the database is the same but now i frequently get
> >> >> > outofmemory
> >> >> > exceptions, and from what i can see, w3wp process keeps requiring
> >> >> > use
> >> >> > of
> >> >> > more
> >> >> > memory. SQL server takes 1.2gb in memory (thats what the task
> >> >> > manager
> >> >> > says)
> >> >> > and w3wp starts at 200-300mb and climbes up to 1.2g in memory before
> >> >> > outofmemory exception and then only iis reset helps.
> >> >> > pls help :)
> >> >>
> >> >>
> >> >>
> >>
> >>
> >>
>
>
>

Re: asp.net app outofmemory

ok, what boot.ini have for switches? there might be some value in using the
/3GB switch here..
what changes have you made to IIS / SQL?

because you have 8GB you are going to want to make sure you enable AWE in
the system and SQL

How is your pagefile set?

get me that info and i an toss together some changes for you...

Justin


"Nedim" wrote in message
news:941BF412-C1C9-4BB0-BDF3-8C8114F25AA6@microsoft.com...
> no, it was the old and the new server.
> the old was an ibm p4 machine with 4gb of memory and windows 2000 server.
> new is the dell with quad core xeon, 8gb of ram and a few disks with
> windows
> 2k3(so basically a beast of a server).
> in the meantime we tried on the old sevrer again, but i get memory errors
> again, so i guess we can rule that out.
> the app is a basic database app. because the database is huge we try to
> cache as much as possible so when the application starts, some smaller
> tables
> that are always needed are put in the Application object, and when a user
> logs in we put most tables in session object (basically one dataset with a
> subset of results that are being shown to the user). Now I dont know how I
> can clear that out of memory - I dont have a webpage_closed event in which
> i
> could clear the tables
>
> "Justin Rich" wrote:
>
>> wait, how is this setup? two servers? does that mean you have IIS on one
>> box
>> and SQL on the other?
>>
>> why don't you explain how this is setup. which apps are where and which
>> has
>> what memory... you might need to approach this differently..
>>
>> Justin
>>
>> "Nedim" wrote in message
>> news:079F544B-5CDF-4C97-9B9A-F1C33DFA44A2@microsoft.com...
>> > Both servers have 4gb of ram (well the latter has 8g but we havent
>> > installed
>> > 64bit windows on it yet). will try puting a lot more .dispose in the
>> > hopes
>> > of
>> > it helping.
>> > but i observed the web server process today and it just kept taking
>> > more
>> > and
>> > more memory, never releasing it (it takes 3mb when i log onto a web
>> > app,
>> > and
>> > takes more as i work thru it, but when i close the browser and 20 min -
>> > session expiry time - passes, it still keeps on taking more and more
>> > memory,
>> > the amount of memory never goes down)
>> >
>> > "Justin Rich" wrote:
>> >
>> >> yeah, there is a chance there might be something else wrong here,
>> >> simple
>> >> because it worked ok in 2k and now in 2k3 you have problems.
>> >>
>> >> Typically what you'll see in this case is that both SQL and IIS have a
>> >> copy
>> >> resident in memory (same data in memory twice) and so you want to tell
>> >> one
>> >> of these two systems not to do so much caching. the problem here is
>> >> although
>> >> you can control how much cache they eat, you cant control them wanting
>> >> to
>> >> eat it... and by that i mean, lets say you limit SQL to 500MB of
>> >> memory,
>> >> all
>> >> fine and dandy but the problem is SQL will still attempt to cache as
>> >> much
>> >> as
>> >> it can, basically wants to hold all the data it can, and if you tell
>> >> it
>> >> to
>> >> hold less, its still going to want to have the same data available to
>> >> it,
>> >> so
>> >> it ends up paging a lot (no longer a memory issue, now its a disk
>> >> issue)
>> >> so
>> >> although you can control the SQL memory usage, its not really that
>> >> great
>> >> of
>> >> an idea..
>> >>
>> >> you can do it with in IIS i believe but off hand i dont know, id have
>> >> to
>> >> look around for that one... but, basically its the same deal, IIS
>> >> wants
>> >> the
>> >> same amount of data... paging again...
>> >>
>> >> based on the numbers you have tossed up here im going to assume you
>> >> probably
>> >> only have 2GB of memory.. your best bet would be to toss another 2gb
>> >> in
>> >> this
>> >> system (2k3 standard can only use 4gb total) and you would probably be
>> >> way
>> >> better off...
>> >>
>> >>
>> >> the next, and probably best way to do this, is to do this via code.
>> >> SQL05
>> >> has some advanced cache management... but... thats all i know.. you
>> >> can
>> >> code
>> >> it different, its cool, and it helps.... sorry, only so much time to
>> >> learn
>> >> :)
>> >>
>> >>
>> >> so, buy more memory if you can, otherwise limit the memory usage. you
>> >> can
>> >> tell SQL to use less if you want, which can be done in SSMS via the
>> >> properties of the DB itself.. its in the obvious section of the
>> >> properties,
>> >> memory, go figure :)
>> >>
>> >>
>> >> good luck
>> >>
>> >> Justin
>> >>
>> >> "Nedim" wrote in message
>> >> news:4BC2FC44-0DDD-4688-BF2A-2DBCAB8A1A77@microsoft.com...
>> >> > It is a database app, but i do generally call dispose methods (maybe
>> >> > not
>> >> > in
>> >> > all the places, I will check it and dispore more often), but it
>> >> > seems
>> >> > to
>> >> > grow
>> >> > too rapidly to be just a .dispose problem.
>> >> > how and where do i modify the session time out periods and db
>> >> > caching
>> >> > (i'm
>> >> > a
>> >> > rookie administrator, that is, i have no idea what to do after i
>> >> > make a
>> >> > virtual directory :))
>> >> >
>> >> > "Justin Rich" wrote:
>> >> >
>> >> >> object.dispose() :)
>> >> >>
>> >> >> i would assume your code is leaving objects open and the garbage
>> >> >> collector
>> >> >> cant keep up, that is to say, it cant touch it for 20 min until the
>> >> >> session
>> >> >> ends...
>> >> >>
>> >> >> if you cant clean up the code you can modify the session timeout
>> >> >> periods
>> >> >> and
>> >> >> other cache related properties (there is some DB caching you can
>> >> >> control
>> >> >> if
>> >> >> its a DB app)
>> >> >>
>> >> >> i'd try to clean up the code if you can.
>> >> >>
>> >> >> Justin
>> >> >>
>> >> >>
>> >> >>
>> >> >> "Nedim" wrote in message
>> >> >> news:85527EB3-4BA9-4ED5-99A4-7BE8F72F98A6@microsoft.com...
>> >> >> >I have a web application written using asp.net 2.0 and c#. Before
>> >> >> >it
>> >> >> >worked
>> >> >> > on Windows Server 2000 and SQL Server 2000, but recently new
>> >> >> > server
>> >> >> > was
>> >> >> > bought (to facilitate migration to sql2k5), and on it is windows
>> >> >> > server
>> >> >> > 2k3
>> >> >> > r2 and sql server 2k5.
>> >> >> > The app and the database is the same but now i frequently get
>> >> >> > outofmemory
>> >> >> > exceptions, and from what i can see, w3wp process keeps requiring
>> >> >> > use
>> >> >> > of
>> >> >> > more
>> >> >> > memory. SQL server takes 1.2gb in memory (thats what the task
>> >> >> > manager
>> >> >> > says)
>> >> >> > and w3wp starts at 200-300mb and climbes up to 1.2g in memory
>> >> >> > before
>> >> >> > outofmemory exception and then only iis reset helps.
>> >> >> > pls help :)
>> >> >>
>> >> >>
>> >> >>
>> >>
>> >>
>> >>
>>
>>
>>