NameTable questions

[Alexander Gnauck]

Hello,

is there a way to disable or reset the entries in a NameTable?

Background is that is that i create small XmlElements and send them over
the wire with a TCP connection. I can't create XmlElements without
having a document. The XmlElements are only created, but never added to
the document. After i sent them they get disposed. In my code will be
lots of classes derived from Element which help me building my XML. The
problem here is that the NameTable blows up with each XmlElement i create.

Of course i could inherit all my classes from XmlDocument to solve this
issue. But the downside here would be that i have to use ImportNode to
build my XML and always create complete XmlDocuments which is very slow.
And compared to the first solution it needs much more memory. I wrote
some small test cases and profiled them for speed and memory comparisons.

Alex

[John Saunders]

"Alexander Gnauck" <gn****@ag-software.dewrote in message
news:45***********************@newsspool2.arcor-online.net...

Hello,

is there a way to disable or reset the entries in a NameTable?

Background is that is that i create small XmlElements and send them over
the wire with a TCP connection. I can't create XmlElements without having
a document. The XmlElements are only created, but never added to the
document. After i sent them they get disposed. In my code will be lots of
classes derived from Element which help me building my XML. The problem
here is that the NameTable blows up with each XmlElement i create.

Of course i could inherit all my classes from XmlDocument to solve this
issue. But the downside here would be that i have to use ImportNode to
build my XML and always create complete XmlDocuments which is very slow.
And compared to the first solution it needs much more memory. I wrote some
small test cases and profiled them for speed and memory comparisons.

In terms of your performance tests, what did you see about the performance
of something like this:

private XmlDocument _theDocument = new XmlDocument();

....

public void SendElement(string name)
{
XmlElement el = _theDocument.CreateElement("");
_theDocument.AppendChild(el);
// Send el
_theDocument.RemoveChild(el);
}

Removing the element from the document might remove its name from the
nametable.

I'm assuming that you are creating many elements with different names, so
that the XmlNameTable fills up with many different names? It doesn't get
duplicate names, does it? Do you ever reach a steady state as to the number
of names in your application?

John

[Alexander Gnauck]

John Saunders wrote:

In terms of your performance tests, what did you see about the performance
of something like this:

private XmlDocument _theDocument = new XmlDocument();

...

public void SendElement(string name)
{
XmlElement el = _theDocument.CreateElement("");
_theDocument.AppendChild(el);
// Send el
_theDocument.RemoveChild(el);
}

i never added the Element to the document. So my tests look like this:

public void SendElement(string name)
{
XmlElement el = _theDocument.CreateElement("");
XmlElement el2 = _theDocument.CreateElement("");
....

el.AppendChild(el2);
...

// Send el
myConnection.Send(el); // is sending el.OuterXml
}

>
Removing the element from the document might remove its name from the
nametable.

see above

I'm assuming that you are creating many elements with different names, so
that the XmlNameTable fills up with many different names? It doesn't get
duplicate names, does it? Do you ever reach a steady state as to the number
of names in your application?

The element and attribute names are limited in the schema. But the
content is different, and this is what gets stored in the NameTable.
And of course they don't contain duplicates, which is the idea behind
the nametable.
If will try to append the element to the document and remove it after
sending and see if it helps.

Alex

[Alexander Gnauck]

Alexander Gnauck wrote:

If will try to append the element to the document and remove it after
sending and see if it helps.

didn't help. I looks like entries in the nametable will never be removed.

Alex

[John Saunders]

"Alexander Gnauck" <gn****@ag-software.dewrote in message
news:45***********************@newsspool3.arcor-online.net...

Alexander Gnauck wrote:

>If will try to append the element to the document and remove it after
sending and see if it helps.

didn't help. I looks like entries in the nametable will never be removed.

You've probably already thought of this, but you could create a new
XmlDocument object for each logical "chunk" of content, assuming the chunks
are large enough. You obviously wouldn't want to do this if it meant
creating 10,000 instances per second!

John

[Alexander Gnauck]

John Saunders wrote:

You've probably already thought of this, but you could create a new
XmlDocument object for each logical "chunk" of content, assuming the chunks
are large enough. You obviously wouldn't want to do this if it meant
creating 10,000 instances per second!

yes i did. In my tests this was 3-4 times slowerinon client and server
applications. On a server with high load i will have much more than
10.000 instances per second.

Alex