/usr/share/mozart/doc/dpanel/node3.html is in mozart-doc 1.4.0-8ubuntu1.
This file is owned by root:root, with mode 0o644.
The actual contents of the file can be viewed below.
1 2 | <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD><TITLE>3 Interpretations of the Distribtion Panel output</TITLE><LINK href="ozdoc.css" rel="stylesheet" type="text/css"></HEAD><BODY><TABLE align="center" border="0" cellpadding="6" cellspacing="6" class="nav"><TR bgcolor="#DDDDDD"><TD><A href="node2.html#chapter.remote"><< Prev</A></TD><TD><A href="index.html">- Up -</A></TD></TR></TABLE><DIV id="chapter.chapter2"><H1><A name="chapter.chapter2">3 Interpretations of the Distribtion Panel output</A></H1><P>Here we give a couple of examples of the output of the Distribution Panel. We describe a program with a special property and then we show how it is possible to see that property in the Distribution Panel. </P><H2><A name="label8">3.1 RTT fluctuations</A></H2><P>In a client server application where the clients and the servers are involved in heavy comunication even the smallest RTT fluctuations can totaly ruin the performance. We monitor the server and observe strange transients in the RTT graph. The transients seem to come with regular intervals. An intelligent guess is that garbage collection at the clients and the server causes inaccessablity and thus raises the RTT. </P><DIV align="center"><IMG alt="" src="StrangeRTT.gif" id="strangertt.gif"></DIV><P> </P><H2><A name="label9">3.2 Connection Port</A></H2><P>Inspecting the Exported entities frame on a disconnected Mozart emulator shows a port in the scroll window. This is the port that the connection mechanism uses and not a bug. It is allways present when some distribution has been initialized since this always initializes the Connection module. </P><DIV align="center"><IMG alt="" src="TicketPort.gif" id="ticketport.gif"></DIV><P></P><H2><A name="label10">3.3 Unexpected Exports </A></H2><P>Unintential exportation of Modules is a common bug in Mozart applications. With help from the Exported frame one can see all the entities that are exported. </P><DIV align="center"><IMG alt="" src="UxpctExports.gif" id="uxpctexports.gif"></DIV><P> </P><H2><A name="label11">3.4 Mass importation of Variables</A></H2><P>When doing synchrone distributed calls using Variables for passing the answer a lot of temporary variables are created. Binding all the extra variables creates a lot of protocoll action and implies a lot of messages. </P><DIV align="center"><IMG alt="" src="MassImportation.gif" id="massimportation.gif"></DIV><P> </P></DIV><TABLE align="center" border="0" cellpadding="6" cellspacing="6" class="nav"><TR bgcolor="#DDDDDD"><TD><A href="node2.html#chapter.remote"><< Prev</A></TD><TD><A href="index.html">- Up -</A></TD></TR></TABLE><HR><ADDRESS><A href="http://www.sics.se/~erik">Erik Klintskog</A> and <A href="http://www.sics.se/~annan">Anna Neiderud</A><BR><SPAN class="version">Version 1.4.0 (20110908185330)</SPAN></ADDRESS></BODY></HTML>
|