Re: Best practice using large objects in foreach
- From: "Marc Gravell" <marc.gravell@xxxxxxxxx>
- Date: 27 Jul 2006 08:21:40 -0700
No; C is /vastly/ more efficient overall, as the memory footprint is
minimised during processing due to early disposal. In A & B this is
performed by the GC, so you will see (for a large set) the memory usage
ramp for a while, then processing grind to a halt as the GC tears down
the improperly discarded images, and then the memory start ramping up
again. I would anticipate C to stay fairly constant both in terms of
memory footprint and processing rate, and it will put much less stress
on the rest of the system - important in a server environment.
Marc
.
- Follow-Ups:
- Re: Best practice using large objects in foreach
- From: Laura T
- Re: Best practice using large objects in foreach
- From: Marc Gravell
- Re: Best practice using large objects in foreach
- References:
- Best practice using large objects in foreach
- From: Benny
- Re: Best practice using large objects in foreach
- From: Laura T
- Best practice using large objects in foreach
- Prev by Date: Re: Timer not working on my Service.
- Next by Date: Re: Constructors
- Previous by thread: Re: Best practice using large objects in foreach
- Next by thread: Re: Best practice using large objects in foreach
- Index(es):