Re: Caching hash

in reply to Caching hash

What's being slow, the IO of reading it from disk, or do you have some calculation going on in making it? How is it actually stored on disk? The fastest format for that is probably Storable::nstore(\%data, $file); ... Storable::retrieve($file). If you have some long-running process that can hold a copy of the data and you want to use that, is a real copy (over a named pipe or something) really too expensive? How big is your data? Is it immutable?

Comment on Re: Caching hash Download Code

Replies are listed 'Best First'.
Re^2: Caching hash by vit (Friar) on Jun 29, 2009 at 20:45 UTC
The reading is slow. I use Storable and the data size is around 1g. It is processed (calculations) in less then one sec, but read much longer.	[reply]
Re^3: Caching hash by gaal (Parson) on Jun 30, 2009 at 05:22 UTC
That's a lot of data! I bet you don't need it all at once on the transient CGIs, though. Should your long-running process provide a query interface? That way the random scripts that come and go only ask it for the stuff they need. You can memcache the results of these queries if you like. No need to spend 1gb on the cache: experiment with some values, see what your hit rates are.	[reply]

In Section Seekers of Perl Wisdom