Re: Pressuring GC to give up clean up memory.
- From: "Nicholas Paldino [.NET/C# MVP]" <mvp@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Mon, 14 May 2007 17:19:21 -0400
Frank,
Well, yes, it would, but at the cost of increasing the memory of the app
that you are running. It will be a zero-sum game at that point, with no
gains or loss overall.
What you want to do is call the SetProcessWorkingSetSizeEx (along with
the process handle) in order to reduce the working set of your app.
--
- Nicholas Paldino [.NET/C# MVP]
- mvp@xxxxxxxxxxxxxxxxxxxxxxxxxxx
"Frank Rizzo" <none@xxxxxxxx> wrote in message
news:OxF9sAmlHHA.4960@xxxxxxxxxxxxxxxxxxxxxxx
Nicholas Paldino [.NET/C# MVP] wrote:
Frank,
Far be it for me to challenge the powers that be, but is your app
dependent on running on the same exact box as sql server? As a general
guideline, I don't run ANYTHING else on SQL Server boxes that doesn't
need to be there.
I couldn't agree with you more. No, the app does not depend on having sql
server on the same box. I think it is the issue of cost (e.g. requiring
customers to buy another box, another set of win2k3 licenses, etc...).
Anyway, getting back to the original problem: would the code in the top
node of the thread increase pressure on GC?
Regards
.
- References:
- Pressuring GC to give up clean up memory.
- From: Frank Rizzo
- Re: Pressuring GC to give up clean up memory.
- From: Nicholas Paldino [.NET/C# MVP]
- Re: Pressuring GC to give up clean up memory.
- From: Frank Rizzo
- Re: Pressuring GC to give up clean up memory.
- From: Nicholas Paldino [.NET/C# MVP]
- Re: Pressuring GC to give up clean up memory.
- From: Frank Rizzo
- Pressuring GC to give up clean up memory.
- Prev by Date: Re: Pressuring GC to give up clean up memory.
- Next by Date: Re: Show a from immediately
- Previous by thread: Re: Pressuring GC to give up clean up memory.
- Next by thread: Re: Pressuring GC to give up clean up memory.
- Index(es):
Relevant Pages
|
