> > > gc_alloc_new.pbc > > > gc_alloc_reuse.pbc > > > > I don't think these two tests are very interesting. They allocate > > quite large strings, so they don't put much strain on the GC. > > Instead, they measure how fast Parrot is at copying strings. > > I believe that's a very good thing to be testing. If the pool allocates > more memory than it thinks it will need, it will perform less overall > copies at the expensive of larger callocs and worser performance in other > cases.
Erg. Seems that for every email I send, I send out another one correcting/clarifying it. :( I will agree with you that gc_alloc_new isn't really useful as it currently stands. While what it is testing is good, it currently only has five iterations due to the huge amount of memory it is allocating. As such, I plan to give it a slower rampup that should allow for more iterations, while still testing the same thing. Mike Lambert
