|
From: Philippe W. <phi...@sk...> - 2009-05-22 11:02:56
|
>> Testing this on firefox startup gives reasonable result: >> there is about 72000 different jCC stack traces, 4,000,000 elements in these stack traces. >> => so, on a x86, this needs about 20Mb of memory > > So there are around 72000 different calling contexts for heap allocations? That seems to > be manageble, yes. Do you do anything special for contexts with recursion? Nothing special is done for recursion: the "raw" stack of JCCs is stored. > > So if you have this, it would be easy to try whether this is practical at > least for some cases also for the cacheline usage... > >> I still have a few things to cleanup/improve. I will then send the current state of >> the code as a basis to discuss/review (there are for sure points to improve/change/enhance/...) > > Thanks, I am interested ;-) The jCC stack trace stuff will be easy to restructure so that it can be re-used for other things than the heap allocations. But I think this will be better done once you will have had the occasion to do a first review : there are a few pieces of code that I have done by trial and errors, without fully understanding the logic behind the code :). Philippe |