[Mono-bugs] [Bug 78075][Nor] Changed - Mono SSL stack performance/tuning issues

bugzilla-daemon at bugzilla.ximian.com bugzilla-daemon at bugzilla.ximian.com
Mon May 1 18:56:28 EDT 2006

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 flucifredi at ximian.com.


--- shadow/78075	2006-04-12 20:51:36.000000000 -0400
+++ shadow/78075.tmp.9687	2006-05-01 18:56:28.000000000 -0400
@@ -1,22 +1,22 @@
 Bug#: 78075
 Product: Mono: Class Libraries
 Version: 1.1
 OS: unknown
 OS Details: 
-Status: NEEDINFO   
+Status: REOPENED   
 Severity: Unknown
 Priority: Normal
 Component: Mono.Security
 AssignedTo: miguel at ximian.com                            
 ReportedBy: naresh at ximian.com               
 QAContact: mono-bugs at ximian.com
 TargetMilestone: ---
-Cc: crivera at novell.com,james at ximian.com,naresh at novell.com,sebastien at ximian.com
+Cc: crivera at novell.com,flucifredi at ximian.com,james at ximian.com,jtariq at novell.com,naresh at novell.com,sebastien at ximian.com
 Summary: Mono SSL stack performance/tuning issues
 Running ZLM 7, our package downloads (over SSL) are very slow in comparion
 to  ZLM 6.6.2.  This looks like a Mono SSL stack performance issue.
 Filing this to Miguel to discuss this further as this is a performance
@@ -345,6 +345,40 @@
 cipher (AES256) cipher.
 As for removing some ciphers from the list, we run into some problems.
 First the (MS designed) API being used doesn't allow providing extra
 information down to the SSL stack. Second, I still believe it's a
 server side decision and that the API should reflect that.
+------- Additional Comments From flucifredi at ximian.com  2006-05-01 18:56 -------
+Here are the results from a round of testing with ZLM 7, ~100MB single
+RPM file.
+Mono client (stock Avenger build vs Wget against the same *identical*
+server (tomcat in ZLM), same file, same path, same network link.
+Default cypher is presumed to be "apache-standard" AES/256. under
+default config, the monoi client takes 2m7sec to download the 100MB
+rpm. Under the same configuration, wget takes 9 seconds.
+we then start fiddling with the cyphers directive in Tomcat, degradin
+g the cypher to RC4/SHA/128b:
+wget, SSL RC4/128b = 6.24 secs (one-half second less than RSA 256)
+mono client, SSL RC4/128b = 37 secs (7 secs of which install) = 30
+secs net time (97 seconds less than AES/256!)
+-> Naresh, please detail what sort of results do you wish to achieve.
+we have performance 1 order of magnitude slower under RC4 (which is a
+cypher not palatable to the server guys anyway), and two orders under
+AES as a ballpark figure. 
+I did not detect a difference in mono performance between AES 256 and
+AES 128. I suspect the Mono implementation of AES, as other
+cyphersuites in Mono seem to perform *much* faster.
+-> James, can you confirm that we are not chunking any of the reads ?
+the 31 second difference between wget and mono under rc4 is
+unaccounted for.

More information about the mono-bugs mailing list