[Mono-list] Mono 2.0 defeat story...

[Hubert FONGARNAND]

Hi,

    A week ago, i tried to upgrade my mono server from 1.2.6 to the new
2.0 mono version. Bad idea...
We use a custom CMS written in C#, it use to work well with 1.2.6
version.

We had test mono 2.0 on our beta platform since a month and we had no
big problems... But on production servers, the environnment is often
different (multi-processor systems, much more users...). I was confident
with mono 2.0 as it was supposed to be well tested by novell...

The upgrade was really a pain, because we have found at least two bugs
in mono :

https://bugzilla.novell.com/show_bug.cgi?id=433908
https://bugzilla.novell.com/show_bug.cgi?id=434305

These bugs prevent our CMS app to run correctly on mono... In addition
to these bugs we experienced a big memory leak with our mod-mono-server
(it use to take ~60Mb (RSS) with mono 1.2.6, with mono 2.0 it was
growing up to 3Go). So this week end we had some "out of memory"
crash... 
In addition to this memory leak, the website was slowing down... When i
start the mod-mono-server process, the web site speed is good
(~900ms/req) and it was 
getting worse and worse as time... (15s/req) 

This morning i downgrade to 1.9.1 in hope that it would solve my
problems... it solves the two first bugs problems (#433908, #434305);
but not my memory leak problem

So the last thing to do was to revert to the good one 1.2.6... and my
speed and memory problems went away!!!
I hope we could upgrade to mono 2.0 when it becomes more stable! I'm
ready to help mono guys to trac these problems.


best wishes
Hubert FONGARNAND
FIDUCIAL

PS: we already run 1.9.1 on our intranet without any memory leaks
problems, but we don't use our CMS
PS : we run in a load balancing environnement, i've downgraded on only
one server... and keep the other one offline in mono 2.0 to do some
tests...




_________________________________________________

Ce message et les éventuels documents joints peuvent contenir des informations confidentielles.
Au cas où il ne vous serait pas destiné, nous vous remercions de bien vouloir le supprimer et en aviser immédiatement l'expéditeur. Toute utilisation de ce message non conforme à sa destination, toute diffusion ou publication, totale ou partielle et quel qu'en soit le moyen est formellement interdite.
Les communications sur internet n'étant pas sécurisées, l'intégrité de ce message n'est pas assurée et la société émettrice ne peut être tenue pour responsable de son contenu.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.ximian.com/pipermail/mono-list/attachments/20081013/58352ea2/attachment.html