Charles Oliver Nutter schrieb: > Jochen Theodorou wrote: >> Charles Oliver Nutter schrieb:[...] >>> Perhaps there's some confusion here. To me, an inline cache is a >>> specific type of call site cache. I considered Groovy's call site cache >>> to be an inline cache. What do you feel is the difference? >> nothing, just a mixup on my side... sorry for that. I somehow thought >> JRuby would use a PIC, but now I realize that is not the case. >> >> Say, do you invalidate the caches from the outside? Because I always had >> the feeling, this would be a bad idea. Too many references. > > We do, and it seems to work fine. It took a bit of fiddling to get > threading-related issues "mostly" safe without locks though. > > The number of references doesn't seem to be as big a deal as the number > of CallSite objects, but for a typical app like Rails after warmup we're > still only using 55-60MB of heap. Just a lot of small objects.
I asked, because I am searching for a way to make the call site cache less thread sensitive.. for example to be able to get the method while updating the cache at the same time... I also considered a event listener system for meta classes in Groovy... a call site cache could then simply register itself by using a special listener.. of course multi threading and listener are always a dangerous combination... bye blackdrag -- Jochen "blackdrag" Theodorou The Groovy Project Tech Lead (http://groovy.codehaus.org) http://blackdragsview.blogspot.com/ http://www.g2one.com/ --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "JVM Languages" group. To post to this group, send email to jvm-languages@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/jvm-languages?hl=en -~----------~----~----~----~------~----~------~--~---
