If you know what criteria then you only need to remember the users who meet that criteria. It seems like you should be able to work that out somehow so that you are disregarding any info you don't need. Perhaps you could find a way to pair the info down some. Instead of storing everything in a database, just use the database to store your unique id's and the important totals. That should reduce the amount of space needed, and avoid haveing a giant hash in memory. I don't know how that would benchmark against your current strategy but it would seem that even if you can't load the whole data into the database you could figure out just enough to get your answers.
Another solution might be to do a sort on the file thereby grouping your transactions togther, but my guess is that would be just as slow.
Good luck and let us know if you find some cool solution ;)
In reply to Re^3: How do I measure my bottle ?
by eric256
in thread How do I measure my bottle ?
by cbrain
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |