[Mono-list] Mono Issue

Garikai Tachiwona (DSL AK) GarikaiT@datacom.co.nz
Tue, 12 Apr 2005 09:32:11 +1200


This is a multi-part message in MIME format.

------_=_NextPart_001_01C53EDD.EC2A38BA
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi,

=20

The background to our problem is that we are deploying a large website
on mono for a customer, and have the server 'freeze' about 1-2  times a
day. At the freeze points mono takes up between 15-55% of  memory on the
web server, typically consumes around 3% of CPU, and the  website
becomes responsive again if the mono processes are restarted.

=20

The freeze is completely random. When we run strace we get copius output
into the trace logs resulting in a large build-up in the log size. We
are therefore forced to stop the trace because of this. Gdb kills the
running application, so we don't use it.

=20

Is there another way of running the trace for days on-end without
producing voluminous (and perhaps unnecessary) data?

=20

Regards

=20

Garikai Tachiwona


------_=_NextPart_001_01C53EDD.EC2A38BA
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:"Trebuchet MS";
	panose-1:2 11 6 3 2 2 2 2 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:Arial;
	color:windowtext;}
@page Section1
	{size:612.0pt 792.0pt;
	margin:72.0pt 90.0pt 72.0pt 90.0pt;}
div.Section1
	{page:Section1;}
-->
</style>

</head>

<body lang=3DEN-US link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

<p class=3DMsoNormal><font size=3D2 color=3Dgray face=3D"Trebuchet =
MS"><span
style=3D'font-size:10.0pt;font-family:"Trebuchet =
MS";color:gray'>Hi,<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dgray face=3D"Trebuchet =
MS"><span
style=3D'font-size:10.0pt;font-family:"Trebuchet =
MS";color:gray'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dgray face=3D"Trebuchet =
MS"><span
style=3D'font-size:10.0pt;font-family:"Trebuchet MS";color:gray'>The =
background
to our problem is that we are deploying a large website on mono for a =
customer,
and have the server 'freeze' about 1-2 &nbsp;times a day. At the freeze =
points mono
takes up between 15-55% of &nbsp;memory on the web server, typically =
consumes around
3% of CPU, and the &nbsp;website becomes responsive again if the mono =
processes are
restarted.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dgray face=3D"Trebuchet =
MS"><span
style=3D'font-size:10.0pt;font-family:"Trebuchet =
MS";color:gray'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dgray face=3D"Trebuchet =
MS"><span
style=3D'font-size:10.0pt;font-family:"Trebuchet MS";color:gray'>The =
freeze is
completely random. When we run strace we get copius output into the =
trace logs
resulting in a large build-up in the log size. We are therefore forced =
to stop
the trace because of this. Gdb kills the running application, so we =
don&#8217;t
use it.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dgray face=3D"Trebuchet =
MS"><span
style=3D'font-size:10.0pt;font-family:"Trebuchet =
MS";color:gray'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dgray face=3D"Trebuchet =
MS"><span
style=3D'font-size:10.0pt;font-family:"Trebuchet MS";color:gray'>Is =
there another
way of running the trace for days on-end without producing voluminous =
(and
perhaps unnecessary) data?<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dgray face=3D"Trebuchet =
MS"><span
style=3D'font-size:10.0pt;font-family:"Trebuchet =
MS";color:gray'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dgray face=3D"Trebuchet =
MS"><span
style=3D'font-size:10.0pt;font-family:"Trebuchet =
MS";color:gray'>Regards<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dgray face=3D"Trebuchet =
MS"><span
style=3D'font-size:10.0pt;font-family:"Trebuchet =
MS";color:gray'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dgray face=3D"Trebuchet =
MS"><span
style=3D'font-size:10.0pt;font-family:"Trebuchet MS";color:gray'>Garikai
Tachiwona</span></font><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p></o:p></span></font></p>

</div>

</body>

</html>

------_=_NextPart_001_01C53EDD.EC2A38BA--