Following the advice of the ever-helpful (and ever-correct) tilly, I've converted my indexing program to use DBI::SQLite with excellent results!
Because SQLite is a fully relational database, I was able to strip out all of my relationship handling perl which has been proven to be quite pathological with large databases of related objects. Now, the client application will have to be rewritten, and much of the relationship think time will go over to the read-side of the equation, but I'm hopeful that it won't be a significant issue (client reads can take several seconds to poll through a full hierarchy without becoming a major problem).
So, I believe my performance problems have been solved by exporting all relationship handling to a relational database (imagine that!). Thanks to all who offered up suggestions (especially those who pointed out the potentially pathological issues with handling relationship data as the original code was guilty of doing). The upside to all of my problems has been that the rest of my code is extremely streamlined now, and runs considerably more efficiently than it would have had I gotten the database problem solved right the first time.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
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:
Outside of code tags, you may need to use entities for some characters:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, 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, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||