[Mono-bugs] [Bug 70702][Maj] Changed - Performance problem with Remoting

[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 lluis@ximian.com.

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

--- shadow/70702	2004-12-20 15:05:35.000000000 -0500
+++ shadow/70702.tmp.27363	2005-01-18 14:06:17.000000000 -0500
@@ -1,14 +1,14 @@
 Bug#: 70702
 Product: Mono: Class Libraries
 Version: 1.0
-OS: 
+OS: unknown
 OS Details: 
 Status: NEW   
 Resolution: 
-Severity: 
+Severity: Unknown
 Priority: Major
 Component: CORLIB
 AssignedTo: mono-bugs@ximian.com                            
 ReportedBy: sebastien.robitaille@croesus.com               
 QAContact: mono-bugs@ximian.com
 TargetMilestone: ---
@@ -49,6 +49,21 @@
 Same results for tests 3 and 4.
 
 How often does this happen? 
 Always.
 
 Additional Information:
+
+------- Additional Comments From lluis@ximian.com  2005-01-18 14:06 -------
+I've been benchmarking the test case and I can't see clear bottlenecks
+in the results. In this case, performance can only be improved by
+doing low level optimizations in corlib and the runtime. I'll work on
+some of those, but don't expect big performance improvements at short
+term. Why then the server side is performing almost as fast as MS.NET?
+Because the server side remoting infrastructure is not as complex as
+the server side.
+
+Just for the record, these are some areas of improvement:
+* Improve the performance of Type.AssemblyQualifiedName.
+* Avoid using DateTime.Now in the connection pool
+* Check for OneWay attribute in the runtime (maybe embed the result in
+the remoting wrapper?)