> Have in mind that reporting errors back to us (either via > bugzilla.novell.com or in this mailing list) is the best way to get these > issues fixed eventually :) You're right, I will do that.
> It's not really to be expected, but these things do happen. I think you > have > hit something that for some reason is faster in mono (maybe our > implementation of some of the base class libraries you use have been more > optimized, or you hit something in the jit we happen to generate better > code > for). It's hard to say without knowing exactly what is running faster in > your application. > > And your sanity should be checked by tests confirming that mono gives the > same output as on windows :) If that is the case, you should have nothing > to > worry about. If not, please file bugs and we'll fix them. I didn't even try the stress tests until after the unit tests were successfully executed under mono and I was satisfied that everything was running smoothly. From what you're saying, I guess I'll just chalk this up as a significant mono improvement/optimization over some part of .Net and not worry about it. Nick -- View this message in context: http://n4.nabble.com/Mono-2-6-3-and-performance-tp2017537p2018522.html Sent from the Mono - VB mailing list archive at Nabble.com. _______________________________________________ Mono-vb mailing list [email protected] http://lists.ximian.com/mailman/listinfo/mono-vb
