Memory's not your problem with that code. CPU time is. You have a very tight loop that doesn't relinquish control. If you don't need millisecond precision (and if you're not using an RTOS, it's not guaranteed anyway), throw in a
sleep call. You might also appease the style police with a
while loop, but do what you like there.
Memory probably isn't a problem, because Unixy operating systems use copy-on-write techniques when forking a kid. That's why fork is so fast -- the cloned process actually uses the same memory pages as the parent. Only when the kid changes (or writes to) a page is a fresh page allocated. If your hypothetical 50 megabyte program only changes a couple of variables in the kid process, only a couple of pages (probably 4 kilobytes in size on a 32-bit machine) will be unshared.
Of course, you could write a dedicated program to handle events, perhaps with POE or Schedule::Cron, and have it listen on a pipe for events to schedule.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.