Front page | perl.perl5.porters |
Postings from March 2007
On Fri, Mar 23, 2007 at 09:06:46PM +0000, Nicholas Clark wrote: > x86 Linux is fairly sane, although valgrind's malloc reacts more badly to > all the free()ing implied by PERL_DESTRUCT_LEVEL=2 than the regular glibc > malloc does: > > 30677 run normally > > 22.10user 0.27system 0:22.90elapsed 97%CPU (0avgtext+0avgdata 0maxresident)k > 0inputs+0outputs (0major+26074minor)pagefaults 0swaps > 30677 run with PERL_DESTRUCT_LEVEL=2 > > 22.03user 0.25system 0:22.89elapsed 97%CPU (0avgtext+0avgdata 0maxresident)k > 0inputs+0outputs (0major+26076minor)pagefaults 0swaps > > 30677 run under valgrind > > 1188.06user 4.12system 20:13.82elapsed 98%CPU (0avgtext+0avgdata 0maxresident)k > 0inputs+0outputs (15major+29142minor)pagefaults 0swaps > > 30677 under valgrind with PERL_DESTRUCT_LEVEL=2 > > 1188.40user 3.89system 20:13.49elapsed 98%CPU (0avgtext+0avgdata 0maxresident)k > 0inputs+0outputs (1major+29365minor)pagefaults 0swaps > > 30678 > > 22.68user 0.26system 0:23.48elapsed 97%CPU (0avgtext+0avgdata 0maxresident)k > 0inputs+0outputs (0major+26079minor)pagefaults 0swaps > > 30678 under valgrind > > 1423.25user 4.97system 24:14.31elapsed 98%CPU (0avgtext+0avgdata 0maxresident)k > 0inputs+0outputs (0major+28904minor)pagefaults 0swaps 30678 run with PERL_DESTRUCT_LEVEL=2 2007.42user 5.51system 34:07.60elapsed 98%CPU (0avgtext+0avgdata 0maxresident)k 0inputs+0outputs (0major+26081minor)pagefaults 0swaps 30678 under valgrind with PERL_DESTRUCT_LEVEL=2 11894.58user 54.79system 3:22:35elapsed 98%CPU (0avgtext+0avgdata 0maxresident)k 0inputs+0outputs (0major+28968minor)pagefaults 0swaps I think you can see why I didn't wait for that one before sending the e-mail. :-( Nicholas ClarkThread Previous | Thread Next