in reply to Re: Reducing memory footprint when doing a lookup of millions of coordinates
in thread Reducing memory footprint when doing a lookup of millions of coordinates

Hi mellon85 and moritz,

Thank you for your replies.

I definitely like the idea of the database. I think this will work very well in the context of the rest of the program I'm writing.

I'm thinking I could distribute the SQLite database file, preloaded with the feature data and indexed, with the software and query it when needed!

Many thanks,

Rich
  • Comment on Re^2: Reducing memory footprint when doing a lookup of millions of coordinates

Replies are listed 'Best First'.
Re^3: Reducing memory footprint when doing a lookup of millions of coordinates
by admiral_grinder (Pilgrim) on Feb 28, 2011 at 20:58 UTC

    The database is a really good idea. I doubt that SQLite keeps the whole database file in memory itself. Could even locate the file to ram disk or similar as a speed bonus.

    You can still use the same code though to do the lookups (with minor modifications):

    1. Get a unique list of all chr.
    2. Foreach chr retrieve all entires (using retrieve_hashref)
    3. use existing code (but work on hashrefs).