Re: TAP::Harness uses lots of RAM to store test results

2013-04-11 Thread Buddy Burden
Nicholas, tl;dr: TAP::Harness uses lots of RAM to store test results Particularly lots and lots for millions of little ok\ns It would be nice if it didn't use lots of RAM when storing things that mostly pass. Yes, I ran into this before.(*) I was referred to a portion of the Test::Builder

Re: TAP::Harness uses lots of RAM to store test results

2013-04-11 Thread Nicholas Clark
On Thu, Apr 11, 2013 at 10:24:35AM -0700, Buddy Burden wrote: Nicholas, tl;dr: TAP::Harness uses lots of RAM to store test results Particularly lots and lots for millions of little ok\ns It would be nice if it didn't use lots of RAM when storing things that mostly pass. Yes, I ran

TAP::Harness uses lots of RAM to store test results

2013-04-10 Thread Nicholas Clark
tl;dr: TAP::Harness uses lots of RAM to store test results Particularly lots and lots for millions of little ok\ns It would be nice if it didn't use lots of RAM when storing things that mostly pass. So, the long(er) story. I use to be able to build and test blead on my Raspberry Pi. Now it runs

Re: TAP::Harness uses lots of RAM to store test results

2013-04-10 Thread Mark Stosberg
Which makes me wonder - just how much memory is TAP::Parser using. In particular, is TAP::Parser using the same amount of memory to store 65850 oks as it would to store some mix of 65850 oks and not oks? Which I'm starting to think, for large test suites, isn't that efficient. Most tests