Those forked processes are not really taking up all that memory. The copy-on-write feature of Linux (and most modern OSes) makes them share all of the read-only parts of the parent process, although you can't see this in top. To prove it to yourself, look at the output of free and then spawn a few copies. You'll see you don't actually lose a GB of RAM each time.
Perl threads typically use more RAM than forked processes. This is because they copy every data structure except the ones you mark as shared and get no copy-on-write help from the OS.
-
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.
|