Yes you are correct , but when I am going to develop
a new and small OS based on the linux kernel I have to take care all the low level parameters ,
so please help me out !
| [reply] [Watch: Dir/Any] |
| [reply] [Watch: Dir/Any] |
Of course, reading Tanenbaum and then trying to use Linux is not necessarily for everybody :). But having a general grasp of operating systems is recommendable and I assume that Tanenbaum knows how to teach the basics of operating systems in general and the specifics of a good operating system as well.
| [reply] [Watch: Dir/Any] [d/l] |
The Perl memory management model is both simple and high performance.
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'.
| [reply] [Watch: Dir/Any] |
Can't say i've noticed any of my scripts memory usage growing over time, (over a few days anyway.) But then again, windows is a complete liar sometimes with regards to memory usage.
I'm just curious, do you have an example script that produces this behaviour?
| [reply] [Watch: Dir/Any] |