For me, SmalltalkImage current vmStatisticsReportString
...works best. If you run this twice, the second time it prints the diff compared to the previous run. So if you print the following three lines SmalltalkImage current vmStatisticsReportString. self runSomeCode. SmalltalkImage current vmStatisticsReportString you'll get the number and time of full and incremental GC cycles while running your code (of course there may have been other processes active in between which may affect the results). It's also a good idea to force a full GC before. Adrian On Aug 23, 2011, at 12:57 , Mariano Martinez Peck wrote: > On Tue, Aug 23, 2011 at 11:11 AM, Andrew P. Black <bl...@cs.pdx.edu> wrote: > >> >> On 17 Aug 2011, at 14:24 , Igor Stasenko wrote: >> >>> yes.. except one thing: since contexts are allocated on heap, it means >>> more work for GC, >>> then it explains that it degrading linearly. >>> >>> Andrew, can you play with GC parameters, like increase number of >>> allocations between incremental GCs etc? >> >> How do I do that? >> >> > > Check method category "vm parameters" in SmalltalkImage. > > >> Is there a gc monitor, that will show me how much time the gc is taking, or >> how many times the incremental gc is running? >> >> > Yes, open "System" -> "Vm statistics" > > >> Andrew >> >> >> > > > -- > Mariano > http://marianopeck.wordpress.com
