[Mono-bugs] [Bug 76400][Nor] Changed - DateTime.Parse allocates 17 kb / call

[bugzilla-daemon at 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 at users.sf.net.

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

--- shadow/76400	2005-10-10 17:56:26.000000000 -0400
+++ shadow/76400.tmp.15886	2005-10-10 18:09:59.000000000 -0400
@@ -1,14 +1,14 @@
 Bug#: 76400
 Product: Mono: Class Libraries
 Version: 1.0
-OS: 
+OS: unknown
 OS Details: 
 Status: NEW   
 Resolution: 
-Severity: 
+Severity: Unknown
 Priority: Normal
 Component: CORLIB
 AssignedTo: mono-bugs at ximian.com                            
 ReportedBy: bmaurer at users.sf.net               
 QAContact: mono-bugs at ximian.com
 TargetMilestone: ---
@@ -35,6 +35,20 @@
 reduced.
 
 ------- Additional Comments From bmaurer at users.sf.net  2005-10-10 17:56 -------
 Created an attachment (id=15897)
 Profile (loopcount = 1,000)
 
+
+------- Additional Comments From bmaurer at users.sf.net  2005-10-10 18:09 -------
+Already got a small win in svn, killed the allocations from
+char.tostring and the boxing of chars. Saves ~4 kb / call. I now do
+the 10,000 count loop in about 1.5 seconds (vs 1.9).
+
+2005-10-10  Ben Maurer  <bmaurer at ximian.com>
+
+        * DateTimeFormatInfo.cs: Rather than having a + ' ' + b, have a +
+        " " + b. This lets us avoid 1) boxing the char and 2) calling
+        char.ToString. Results in a fairly substantial savings on
+        DateTime.Parse.
+
+r51532