[Ecls-list] Improving CLOS?
Julian Stecklina
js at alien8.de
Fri Mar 19 02:23:34 UTC 2010
Waldek Hebisch <hebisch at math.uni.wroc.pl> writes:
> They report (depending on number of parameters) between 218 and 77
> milions of dispatching calls per second on 2.5 GHz Core 2. That is
> 11-33 clocks per call. I am affraid that with current call convention
> ECL has no chance to match that: current ECL indirect call costs
> about 75 clocks, so even if dispatching cost would be reduced to 0,
> ECL still would be much slower.
This is surprisingly expensive. Might be a branch prediction miss due to
the indirect call?
Regards,
--
Julian Stecklina
The day Microsoft makes something that doesn't suck is probably the day
they start making vacuum cleaners - Ernst Jan Plugge
More information about the ecl-devel
mailing list