2009/11/13 Cédrick Béler <cdric...@gmail.com>: > > > >> No, please no more inilining hacks. :) >> If someone wants to run everything at light speed - just code in C, >> but leave smalltalk honoring the >> message passing. >> And besides, these tricks won't make any difference when having good >> inlining JIT. >> In bytecode, they just add a complexity to compiler and headache to >> developers. >> > > I agree but I asked beacause I'll make student use this method and wasn't > sure of the explanation. > > Also, some asked me about the performance of Pharo/Smalltalk in general. > > I did this counter in C++ and Smalltalk. > > I get a 10x difference between C++ and Pharo, the inlined version, and > therefore a 40x whith the other one. > > So does this number seems reasonnably true to you ?
You are counting wrong numbers. Please count the time you have to spend to interpret closures in C++, and then using them run arbitrary code in the loop, then we will talk again when you done :) > What would be the order of magnitude with a JIT ? > > TIA, > > Cédrick > > > _______________________________________________ > Pharo-project mailing list > Pharo-project@lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- Best regards, Igor Stasenko AKA sig. _______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
