[Mono-bugs] [Bug 59537][Nor] Changed - improve NameTable performance

[bugzilla-daemon@bugzilla.ximian.com]

Please do not reply to this email- if you want to comment on the bug, go to the
URL shown below and enter your comments there.

Changed by bmaurer@users.sf.net.

http://bugzilla.ximian.com/show_bug.cgi?id=59537

--- shadow/59537	2004-06-03 07:11:31.000000000 -0400
+++ shadow/59537.tmp.9266	2004-06-03 07:44:44.000000000 -0400
@@ -49,6 +49,24 @@
 
 What do you say ?
 
 ------- Additional Comments From atsushi@ximian.com  2004-06-03 07:11 -------
 Please, attach the example code so that we can examine not only speed
 but also memory consumption.
+
+------- Additional Comments From bmaurer@users.sf.net  2004-06-03 07:44 -------
+Hello,
+
+Origionally, we had a design much like the one you suggested: create a
+new string, and call .GetHashCode. The issue is that the char []
+version is the most commonly called. The XML parser will be reading in
+a file, and have data in an array:
+
+{ ..., '<', 't', 'a', 'g', '>', ...}
+
+When we did the new string method, there was much more memory
+allocation. This ended up killing performance.
+
+One thing we can do is to use unsafe code to avoid some of the
+overhead of Array Bounds Checking.
+
+