[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-08 05:16:38.000000000 -0400
+++ shadow/59537.tmp.30092	2004-06-09 10:52:46.000000000 -0400
@@ -267,6 +267,12 @@
 That's wierd. something must be rotten in GetHashCode() , after all,
 it should do the same job.
 If this is the situation I think that solving String::GetHashCode()
 problem will give you "pretty big pref boost". I know Sun and Micosoft
 invested some native code to make this hash method rock. (in fact they
 invested alot in the class String).
+
+------- Additional Comments From bmaurer@users.sf.net  2004-06-09 10:52 -------
+Ok, atsushi's test case is not quite right. He does not take advantage
+of the new impl that much. Basically, the problem is that we are not
+querying on names that are already in the table -- every query in
+eno's benchmark is unique. This is not how the code is designed.