Databases use structures like B-trees for indexing and sorting and are pretty good in balancing these trees between RAM and disk. °
They optimize the trade-off between memory and time.
Perl is pretty bad in sorting linear stuff which is part in RAM and part on disk.
(Well you could tie an AoA to a file representing a table. Sorting that array would go without much RAM but mean constant overhead with each access. This is certainly worth a shot, but as I said DBs have this already optimized.)
Cheers Rolf
(addicted to the Perl Programming Language :)
Wikisyntax for the Monastery
°) from WP B-tree
Unlike other self-balancing binary search trees, the B-tree is well suited for storage systems that read and write relatively large blocks of data, such as disks ...
... for the purpose of efficiently managing index pages for large random access files. The basic assumption was that indexes would be so voluminous that only small chunks of the tree could fit in main memory.
In reply to Re^3: efficient perl code to count, rank (B-tree)(update)
by LanX
in thread efficient perl code to count, rank
by Perl_Noob2021
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |