Ok. I see what you're getting at now. The table was very helpful. This is a really unique solution among the ones I've seen so far. Once I get this module finished, I think I may go back and do benchmarks between my chosen solution (the one involving granularity-based marks and from those, incremental on-off logs) and this one. If I do, I'll letcha know how they come out. If these logs you've thought up were separated somehow (by day into files, or something) the seek time wouldn't be too bad at all.
My officemate suggested last night that a tree-based system might be devised that could do any search in less than N time. We didn't get it quite worked out, but I'm gonna keep at it and see what I can come up with.
--
Love justice; desire mercy.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.