[Pharo-project] Remove #class as a Compiler optimization

Marcus Denker marcus.denker at inria.fr
Tue Apr 5 12:36:04 CEST 2011


On Apr 5, 2011, at 12:32 PM, Mariano Martinez Peck wrote:

> 
> 
> On Tue, Apr 5, 2011 at 12:09 PM, Igor Stasenko <siguctua at gmail.com> wrote:
> On 5 April 2011 11:33, Mariano Martinez Peck <marianopeck at gmail.com> wrote:
> > So....I tried with running all tests of a PharoCore 1.3 and I've got this:
> >
> > cog vm  with optimization
> > Time to run all tests:116506
> >
> > cog vm  without optimization
> > Time to run all tests:121930
> >
> > 121930 - 116506 ----> 5424
> > ((5424 * 100) / 116506) asFloat ---> 4.655554220383499
> >
> > So...in Cog, running all test, there is an overhead of 4.6%
> >
> > Do we want to pay it ?
> >
> > I would...but I am all ears.
> >
> 5% for #class message?
> this is too much. or you also removed other optimized sends?
> 
> 
> Only that one. For #== I got 4.3. And doing both together (#class and #==) I got 9.05% :(
> 
> And removing the #class optimization in a Interpreter VM gives me almost as in cog: 4.7%
> 
> maybe I am doing something wrong...
> 
can you try in 1.2? We did some compiler changes that are not yet fully done....
e.g.

Issue 3940:	BlockNode has undeclared ivar optimizedMessageNode





--
Marcus Denker  -- http://www.marcusdenker.de
INRIA Lille -- Nord Europe. Team RMoD.




More information about the Pharo-project mailing list