Forgot to mention,<br><br>From the commandline,<br><br>>>> from cherrypyserver import run,shutdown<br>>>> run()<br><br>to start the server which is then accessible @ <a href="http://localhost:9999/">http://localhost:9999/
</a><br><br><div><span class="gmail_quote">On 3/15/07, <b class="gmail_sendername">M. David Peterson</b> <<a href="mailto:xmlhacker@gmail.com">xmlhacker@gmail.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
In the ongoing development of the Xameleon (merge between Amplee/AtomicXML) application Sylvain and I have been running into various hurdles, none of which have been insurmountable, but the most recent of which I am having trouble attempting to understand the problem.
<br><br>Background: A few days back we discovered that attempting to startup and run Amplee via CherryPy we were reaching upwards of 150megs just to start up the server. After a bit of digging we discovered that saving the assemblies (-X:SaveAssemblies) during the first run, and then restarting the app dropped the resource usage meter from 150 to below 50 megs, something that was definitely within reason.
<br><br>That said, assuming that the same resources would be consumed for both a stand alone implementation, as well as a ClickOnce implementation (both ClickOnce and standalone were both consuming ~150megs before saving the assemblies), I was surprised to discover recently that there is ~45meg increase in the ClickOnce implementation over the standalone.
<br><br>You can access the standalone files @ <a href="http://extf.googlecode.com/files/Xameleon.WebApp.0.1.15.zip" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">http://extf.googlecode.com/files/Xameleon.WebApp.0.1.15.zip
</a> and the ClickOnce app @ <a href="http://xameleon.org/Personal.Web.Platform/ClickOnce/" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
http://xameleon.org/Personal.Web.Platform/ClickOnce/</a> <br><br>These both come from the exact same code base/project @ <a href="http://extf.googlecode.com/svn/trunk/Xameleon.WebApp/" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
http://extf.googlecode.com/svn/trunk/Xameleon.WebApp/
</a> and I've verified that the same compiled .exe modules exist in both implementations, so as far as I can tell, this isn't a situation where I simply forgot to include some of the compiled Python modules in the ClickOnce implementation, accounting for the difference in resource usage as a result.
<br><br>Any ideas as to what might be the issue, and how to solve it?<br><br>Thanks in advance!<br clear="all"><span class="sg"><br>-- <br>/M:D<br><br>M. David Peterson<br><a href="http://mdavid.name" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
http://mdavid.name</a> | <a href="http://www.oreillynet.com/pub/au/2354" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
http://www.oreillynet.com/pub/au/2354</a> | <a href="http://dev.aol.com/blog/3155" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">http://dev.aol.com/blog/3155</a>
</span></blockquote></div><br><br clear="all"><br>-- <br>/M:D<br><br>M. David Peterson<br><a href="http://mdavid.name">http://mdavid.name</a> | <a href="http://www.oreillynet.com/pub/au/2354">http://www.oreillynet.com/pub/au/2354
</a> | <a href="http://dev.aol.com/blog/3155">http://dev.aol.com/blog/3155</a>