RS Memory Leak?

I am testing the SQL Web Reporting Services and noticed that the memory
usage of sqlservr.exe and w3wp.exe remain at a high level even though all
the client applications were closed. Is this a known issue? Is there a fix?
Thanks.
FabianThe two exe's you mention have nothing directly to do with Reporting
Services. Reporting Services is an asp.net application that uses SQL Server
as an object store.
Here is a good article about how SQL Server manages memory:
http://support.microsoft.com/default.aspx?scid=kb;en-us;321363
An excerpt from the article:
>>>>>>>>>>
When you start SQL Server, SQL Server memory usage may continue to steadily
increase and not decrease, even when activity on the server is low.
Additionally, the Task Manager and Performance Monitor may show that the
physical memory available on the computer is steadily decreasing until the
available memory is between 4 to 10 MB.
This behavior alone does not indicate a memory leak. This behavior is normal
and is an intended behavior of the SQL Server buffer pool.
By default, SQL Server dynamically grows and shrinks the size of its buffer
pool (cache) depending on the physical memory load reported by the operating
system. As long as enough memory is available to prevent paging (between 4 -
10 MB), the SQL Server buffer pool will continue to grow. As other processes
on the same computer as SQL Server allocate memory, the SQL Server buffer
manager will release memory as needed. SQL Server can free and acquire
several megabytes of memory each second, allowing it to quickly adjust to
memory allocation changes.
>>>>>>>>>>>
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Fabian Cevallos" <fcevallos@.bellsouth.net> wrote in message
news:Ow$lZ6w3EHA.3820@.TK2MSFTNGP11.phx.gbl...
>I am testing the SQL Web Reporting Services and noticed that the memory
>usage of sqlservr.exe and w3wp.exe remain at a high level even though all
>the client applications were closed. Is this a known issue? Is there a
>fix? Thanks.
> Fabian
>|||Thanks for the link. It provided good information.
"Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote in message
news:%230TWWmz3EHA.404@.TK2MSFTNGP10.phx.gbl...
> The two exe's you mention have nothing directly to do with Reporting
> Services. Reporting Services is an asp.net application that uses SQL
> Server as an object store.
> Here is a good article about how SQL Server manages memory:
> http://support.microsoft.com/default.aspx?scid=kb;en-us;321363
> An excerpt from the article:
>>>>>>>>>>
> When you start SQL Server, SQL Server memory usage may continue to
> steadily increase and not decrease, even when activity on the server is
> low. Additionally, the Task Manager and Performance Monitor may show that
> the physical memory available on the computer is steadily decreasing until
> the available memory is between 4 to 10 MB.
> This behavior alone does not indicate a memory leak. This behavior is
> normal and is an intended behavior of the SQL Server buffer pool.
> By default, SQL Server dynamically grows and shrinks the size of its
> buffer pool (cache) depending on the physical memory load reported by the
> operating system. As long as enough memory is available to prevent paging
> (between 4 - 10 MB), the SQL Server buffer pool will continue to grow. As
> other processes on the same computer as SQL Server allocate memory, the
> SQL Server buffer manager will release memory as needed. SQL Server can
> free and acquire several megabytes of memory each second, allowing it to
> quickly adjust to memory allocation changes.
>>>>>>>>>>>
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "Fabian Cevallos" <fcevallos@.bellsouth.net> wrote in message
> news:Ow$lZ6w3EHA.3820@.TK2MSFTNGP11.phx.gbl...
>>I am testing the SQL Web Reporting Services and noticed that the memory
>>usage of sqlservr.exe and w3wp.exe remain at a high level even though all
>>the client applications were closed. Is this a known issue? Is there a
>>fix? Thanks.
>> Fabian
>>
>|||Could this be related to article 885268?
I'm experiencing the same problem.
-Bill
"Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote in message
news:%230TWWmz3EHA.404@.TK2MSFTNGP10.phx.gbl...
> The two exe's you mention have nothing directly to do with Reporting
> Services. Reporting Services is an asp.net application that uses SQL
Server
> as an object store.
> Here is a good article about how SQL Server manages memory:
> http://support.microsoft.com/default.aspx?scid=kb;en-us;321363
> An excerpt from the article:
> >>>>>>>>>>
> When you start SQL Server, SQL Server memory usage may continue to
steadily
> increase and not decrease, even when activity on the server is low.
> Additionally, the Task Manager and Performance Monitor may show that the
> physical memory available on the computer is steadily decreasing until the
> available memory is between 4 to 10 MB.
> This behavior alone does not indicate a memory leak. This behavior is
normal
> and is an intended behavior of the SQL Server buffer pool.
> By default, SQL Server dynamically grows and shrinks the size of its
buffer
> pool (cache) depending on the physical memory load reported by the
operating
> system. As long as enough memory is available to prevent paging (between
4 -
> 10 MB), the SQL Server buffer pool will continue to grow. As other
processes
> on the same computer as SQL Server allocate memory, the SQL Server buffer
> manager will release memory as needed. SQL Server can free and acquire
> several megabytes of memory each second, allowing it to quickly adjust to
> memory allocation changes.
> >>>>>>>>>>>
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "Fabian Cevallos" <fcevallos@.bellsouth.net> wrote in message
> news:Ow$lZ6w3EHA.3820@.TK2MSFTNGP11.phx.gbl...
> >I am testing the SQL Web Reporting Services and noticed that the memory
> >usage of sqlservr.exe and w3wp.exe remain at a high level even though all
> >the client applications were closed. Is this a known issue? Is there a
> >fix? Thanks.
> >
> > Fabian
> >
> >
>