Re: Interpreting Mission Control numbers for indy

2013-09-19 Thread George Marrows
Christian -- Duncan Macgregor and I have a large desktop application that makes very heavy use of indy. As Duncan reported recently, we're also seeing increased memory usage and (probably) decreased performance under u40. Will contact you privately with details of how we can get you access. -- G

Re: Interpreting Mission Control numbers for indy

2013-09-18 Thread Christian Thalinger
On Sep 18, 2013, at 1:39 AM, Charles Oliver Nutter wrote: > I've been playing with JMC a bit tonight, running a user's application > that's about 2x slower using indy than using trivial monomorphic > caches (and no indy call sites). I'm trying to understand how to > interpret what I see. > > In

Re: Interpreting Mission Control numbers for indy

2013-09-18 Thread Charles Oliver Nutter
A bit more on performance numbers for this application. With no indy, monomorphic caches...the full application (a data load) runs in about a minute. I fully recognize that this is a short run, but JMC seems to indicate the bulk of code has compiled well before the halfway point. With 7u40 or 8,

Interpreting Mission Control numbers for indy

2013-09-18 Thread Charles Oliver Nutter
I've been playing with JMC a bit tonight, running a user's application that's about 2x slower using indy than using trivial monomorphic caches (and no indy call sites). I'm trying to understand how to interpret what I see. In the Code/Overview results, where it lists "hot packages", the #1 and #2