Re^4: Efficient way to handle huge number of records?

Yes, even Windows 32 bit XP can go to 3GB for a user, but there can be problems if that feature is enabled.

This appears to be a job for a DB, if many searches will be performed after the DB is "built" (initialized and indexed).

From the problem statement, I think that SQLite will do the job just fine. At such time that it does not, then the SQL will work on another DB.

Comment on Re^4: Efficient way to handle huge number of records?

Replies are listed 'Best First'.
Re^5: Efficient way to handle huge number of records? by BrowserUk (Patriarch) on Dec 11, 2011 at 13:46 UTC
This appears to be a job for a DB, if ... See Item 3. The "if" is crucial. Personally, I can see no logic at all in running a 32-bit OS on 64-bit hardware. 32-bit Perl on 64-bit OS has one advantage -- at least in the Windows world -- that of more XS modules build successfully. But even on windows, the stuff that doesn't tends to be either abandon-ware or the weird esoteric stuff like POE and Coro which either will never work with Windows or despite themselves if they do. But for the most part, a 64-bit build of Perl on a 64-bit OS with 8/16/32/64GB of ram just makes doing anything involving the huge datasets that typify genomic work so much easier. When you can pick up 8GB of ram for Ł29, it makes no sense to try and squeeze the large datasets typified by genomic work through 2 or 3GB memory pools. With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday' Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error. "Science is about questioning the status quo. Questioning authority". In the absence of evidence, opinion is indistinguishable from prejudice. The start of some sanity?	[reply]
Re^6: Efficient way to handle huge number of records? by Marshall (Canon) on Dec 11, 2011 at 14:21 UTC
I think that this XS module build problem on 64 bit machines is going to get solved. It is inevitable. Evolve or die. Like all evolutionary things, it takes some time. If the OP's data fits into RAM, then why the heck not? I have no problem with that. A hash table and RAM access is gonna beat any kind of DB hands down!	[reply]