I don't think the problem is the I/O of loading those perl scripts, the perl executable or associated perl libraries.
Normally, the Linux VM subsystem should automatically cache frequently read files in RAM, in order to speed up future reads. If you users are running the same perl script(s) thousands of times per day, then those scripts, and everything required to run them should be in RAM most of the time.
The only situation I can think of where those files would not get cached, are either your system is under severe memory pressure. (Try running free and see how much swap is in use, it ought to be none or very little on a modern server system), or you or someone else has been tweaking the VM subsystem tunable parameters, and stuffed them up. I don't think either scenario is likely.
As SuicideJunkie has suggested, you could create a RAM disc, and copy your perl install there. That would force your Kernel to keep the files in RAM, along with a load of other irrelevant files. I don't think that is a good idea. If your system is under memory pressure, the data will get moved to swap anyway, and if not it will make no difference.
Instead I think you should look for other causes of your poor performance. Unfortunately, I can't come up with any constructive suggestions on that.
Sorry I can't be positive help, but I do think you are chasing the wrong culprit.
In reply to Re: Techniques to cache perl scripts into memory ?
by chrestomanci
in thread Techniques to cache perl scripts into memory ?
by fx
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |