BrowserUK, didn’t you “forget” to log in?
There is nothing “personal,&rduo; nor technically un-informed, about my specific comments here, most specifically including the comment about processes vs. threads. Threads in every programming system share a single process-level context; hence, the same memory-management system. During the course of execution, a “leaky” procedure can, in time, accumulate an excess amount of unrecoverable memory. In a context of threads, that memory is never cleaned-up, whereas by definition the entire context of a process, is.
If the “hari kiri” approach didn’t work, as a way of dealing in a black-box fashion with leaky faucets, then it would not be the case that Apache, nginix, and PSGI (Plack) all have specific means by which to do just that. My comments are technically valid at face value, as they were intended to be. If you have disagreement, then (a) show yourself, and (b) comment about the technical statements, not the Monk making them.
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|
