Rank: Member
Groups: Guest
Joined: 7/29/2005(UTC)
Posts: 7
|
Divided my issues into two separate posts... We are using GraphicsMill.Net 3.1 in a production website runnin IIS 6 and ASP.Net 2.0 Heap size is becoming a big issue. The IIS worker process allocates heap memory in large chunks when GraphicsMill components are called. Like in 5mb chunks for simple transforms of 100k jpg images. We are releasing/disposing of absolutely everything immediately after usage, and our working set remains steady. But the heap allocation seems to be something we can't effect. It grows until all available addresses are used in the memory space and the worker process shuts down and recycles. For us this is typically around 500mb of heap allocation. We really, really don't want to pull the components out of process but are at a loss as to how to control the GraphicsMill heap usage inside the IIS process space. We have narrowed this issue down to pages that use GraphicsMill. Any thoughts here? Environment: -GraphicsMill.Net 3.1 -IIS 6 -ASP.Net 2.0
|
|
|
|
|
|
Rank: Advanced Member
Groups: Guest
Joined: 8/3/2003(UTC)
Posts: 1,070
Thanks: 1 times
Was thanked: 12 time(s) in 12 post(s)
|
Hello, We have fixed similar problem in Graphics Mill for .NET 3.5. Could you download this version from our site: Graphics Mill for .NET 3.5, and try it out? |
|
|
|
|
|
|
|
Rank: Member
Groups: Guest
Joined: 7/29/2005(UTC)
Posts: 7
|
Put 3.5 on the productin boxes. After running for a full day, the heap has not gotten bigger than 20mb and there has been no recycling of the IIS worker process. Seems that (so far) 3.5 fixes the memory usage problems. Thanks for helping solve the problem. -Grady
|
|
|
|
|
|
Forum Jump
You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.