I guess the performance issue that your source is referring to would be the repetitive load and unload of the Perl interpreter.
On a low-end computer this might make a difference.
But, I'd say it's rare.
As other people have already pointed out, crond in itself is very efficient and very reliable.
If you still decide to go for a 24/7 application and also want your 'event'
to take place at a given second in the minute (not 60 seconds after the last event finished)
then I'd propose you to give a look at
Schedule::ByClock.pm
which does just that.
"Livet är hårt" sa bonden.
"Grymt" sa grisen...
In reply to Re: writing looped programs
by Biker
in thread writing looped programs
by tachekent
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |