It would be helpful if you posted some code and example data. This sounds as if you read the entire database into memory. If so, that will certainly slow things down.
Are you using DBI.pm to read the data? A few suggestions:
A tie class may be useful, but a few sub returning data, given a key, is likely to work as well. Of course, all this is speculative and not necessarily useful.
After Compline,
Zaxo
Update: Changed list to numbered format for reference.
Thanks for the extra info on your requirements. I'm sorry to admit that I'm unfamiliar with any of the mechanisms you cite (Apache::ASP, CORBA through the COPE modules). You don't appear to use either CGI.pm or DBI.pm. (Update2: I'm informed that htoug uses DBI.)
You might try #5 'Benchmark' right away, to see where the resource hogs are.
Given your security requirements, #4 is all the more important.
As a design issue, I'd suggest starting from the user interface and seeing how few SQL statements you need to support it.
In reply to Re: Using tie to initialize large datastructures
by Zaxo
in thread Using tie to initialize large datastructures
by htoug
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |