in reply to Re^2: Memory management
in thread Memory management
If you watch the memory "footprint" of a long lived Perl process, you will observe that it grows and never gets smaller. Once Perl has a hunk of memory from the OS, it will never give it back to the OS although Perl will reuse that memory for its own purposes. So a Perl process approaches a maximum size as it runs.
It is possible nowadays to run Perl even on a small embedded system. JAVA or C# have much more complex memory models as well as complex, hard to understand performance "hits".
Perl may or may not be a good implementation language for your system. More and more systems are built with a mixture of languages. Perl is THE "black belt" at processing text. Last year I talked with some folks who write automated commodity trading software. These guys are like 300 feet via fiber optic cable from the exchange - it doesn't get closer than that. What do these guys use to handle the text data? You got it, Perl! What do they use to drive the "middle ware"? You got it, 'C'.
|
|---|
| Replies are listed 'Best First'. | |
|---|---|
|
Re^4: Memory management
by desemondo (Hermit) on Aug 13, 2009 at 11:08 UTC | |
by Marshall (Canon) on Aug 14, 2009 at 12:23 UTC | |
by Anonymous Monk on Aug 14, 2009 at 12:31 UTC | |
by Marshall (Canon) on Aug 14, 2009 at 12:53 UTC | |
by desemondo (Hermit) on Aug 16, 2009 at 11:17 UTC | |
by Marshall (Canon) on Aug 18, 2009 at 16:37 UTC | |
by desemondo (Hermit) on Aug 20, 2009 at 10:04 UTC |