I have an xml document defined by a schema that includes roughtly 1100 types.
When I go to deserialize the root type I notice that the xmlSerializer
creates the nametable and adds all 1100 types (plus some) entries into the
nametable. The problem I'm seeing with the VS Team System performance test
tool is that in addition to the 1100 nametable entries there are over 100,000
strings created. It's become a huge memory hog. What's going on? Is there
any way to minimize this without modifying the underlying xml schema? The
string alone can eat up 33M. Could it be a .Net bug? Help is greatly
appreciated.
Thanks!
Fratt
When I go to deserialize the root type I notice that the xmlSerializer
creates the nametable and adds all 1100 types (plus some) entries into the
nametable. The problem I'm seeing with the VS Team System performance test
tool is that in addition to the 1100 nametable entries there are over 100,000
strings created. It's become a huge memory hog. What's going on? Is there
any way to minimize this without modifying the underlying xml schema? The
string alone can eat up 33M. Could it be a .Net bug? Help is greatly
appreciated.
Thanks!
Fratt