On Tue, Oct 21, 2003 at 03:01:20PM -0700, Ovid wrote: > --- Tim Bunce <[EMAIL PROTECTED]> wrote: > > > I'll look into SQLite. > > > > I'd caution against rushing in any particular direction without some > > profiling information to back it up. > > > > Having said that, I'd strongly recommend switching to Storable first. > > It did have problems but it's now very robust and far, far, faster > > than Data::Dumper+eval. This small change would yield a big gain. > > > > The next step would be to get some profile information. There's > > little point in doing that first as Data::Dumper+eval will dwarf > > time spent elsewhere. > > It's not performance that's killing Devel::Cover when we run tests. It's that the > data structure > for the coverage data appears to be built in-memory and it's so huge that I run out > of memory (and > this is on a machine with a couple of gigs of RAM). > > If it's not the data structure being built but instead is the conversion to > Data::Dumper format, > then ignore what I say :)
It's probably both. Reading and writing Data::Dumper format is much more memory hungry than Storable. Switch to Storable will at least ease the problem. Reduction in memory use beyond that probably requires deeper changes in the logic. I don't have time in the short term to work on the (albeit fairly trivial) change to Storable. If someone can do that and get a new release out then I'll look deeper into the performance issues then. Tim.
