I'm wondering if you ever figured out what was going on here; and if (and how) you
resolved it. Did you have many objects reaching gen2 that were not "for the duration
of the application" objects, which eventually went away, causing lots of (expensive)
gen2 collections?
At 04:12 AM 1/27/2004,
First, if you haven't already, you should checkout the performance info from
the .NET team [1]. Specifically, this article [2] on GC performance may be
valuable. Without understanding how the GC works it is relatively easy to
end up with code that it spending a lot of its time in GC. How high do
Inline...
> -Original Message-
> From: Moderated discussion of advanced .NET topics.
> [mailto:[EMAIL PROTECTED] Behalf Of J. Merrill
> Sent: Wednesday, January 28, 2004 4:19 PM
> To: [EMAIL PROTECTED]
> Subject: Re: [ADVANCED-DOTNET] Garbage collection problem
>
At 03:12 AM 1/27/2004, Bert Roos wrote (in part)
>Hi,
>
>We're having a strange problem that seems to be related to garbage collection. We're
>performing load testing through a load generator tool (LoadRunner). At a certain load
>level, the response times show strange and heavy fluctuations. Requ
Hi,
We're having a strange problem that seems to be related to garbage collection. We're
performing load testing through a load generator tool (LoadRunner). At a certain load
level, the response times show strange and heavy fluctuations. Request handling times
go up by a factor 10 over an exte
