The whole thing looks like to me that you should use a database - which can be accessed using a tied hash. If you don't want to use one you could do the following:
Write a perl script which holds the hash and stays persistent in the background while allowing other perl scripts to query the hash elements using a unix socket or similar interface.
You could even use a tied hash which automatically does the communication for you. Both introduces some runtime latency and you should carefully check if it isn't worse for your application then the load latency at start-up when you reload the hash.
In reply to Re: Keeping hash table in memory
by mscharrer
in thread Keeping hash table in memory
by Anonymous Monk
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |