BTW, I'm glad to see you still working on/maintaining the African Grey variation. I think it is important to maintain alternatives. Who knows, at some point in the future, it may be determined that this is the right way to go. If memory for embedded systems is the only issue, then I could definately see the sources merged and a configure option available to choose the right one. As for the stackwalk, well...you never know.
Anyway, keep up the good work. Tanton ----- Original Message ----- From: "Peter Gibbs" <[EMAIL PROTECTED]> To: "Steve Fink" <[EMAIL PROTECTED]> Cc: "perl6-internals" <[EMAIL PROTECTED]> Sent: Thursday, September 05, 2002 1:57 PM Subject: Re: [Info] African Grey update > Steve Fink wrote: > > > Twice as fast seems like a good thing. Is this with the stackwalk > > disabled? What prevents this from being applied to Parrot now? > > Yes, stackwalk is disabled, as it still isn't required yet. Enabling > stackwalk takes 112 seconds, so the other differences in grey > seem to have very little impact on performance. > > I believe the main reasons for non-applicability (per Dan) are: > 1) Stackwalk is mandated. > I am still waiting for code that requires stackwalk so I can test > some ideas on this. > 2) Buffer headers (and to a lesser extent PMCs) are larger. > It would be interesting to include headers in the reported > memory usage for parrot, as is now done in grey, so the > impact of this can be seen. > > > Is there an easy way to see how many of those collection runs were > > complete, or the total number of pages collected and the total number > > that could have been collected, or some sort of statistic that > > indicates how often the paged collections kick in? > > I'll take a look at this tomorrow. > > Thanks for your interest > -- > Peter Gibbs > EmKel Systems > > > >
