[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Help-smalltalk] Using COMMON/UNCOMMON
From: |
Holger Hans Peter Freyther |
Subject: |
[Help-smalltalk] Using COMMON/UNCOMMON |
Date: |
Sat, 12 Feb 2011 13:28:38 +0100 |
User-agent: |
Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.13) Gecko/20101209 Fedora/3.1.7-0.35.b3pre.fc14 Lightning/1.0b2 Thunderbird/3.1.7 |
Hi Paolo,
on the hype of the micro benchmarking I started to look at GST (mostly to
understand the VM and not so much in making it faster). It appears to me that
when defining COMMON/UNCOMMON to nothing we get a speedup on the
tinyBenchmark. So this means that either some of the COMMON/UNCOMMOM are
placed incorrectly, or that the tinyBenchmark is not what we are optimizing
for and that the COMMON/UNCOMMON are better for some workloads.
Would you be interested in knowing from where this difference is coming? I
could build with gprof and then use lcov and their branch visualization.
holger
Before:
198180762 bytecodes/sec; 6070565 sends/sec
After:
220286113 bytecodes/sec; 6342298 sends/sec
PS: stable-3.2 as of yesterday, on a Fedora14/i686 system.
- [Help-smalltalk] Using COMMON/UNCOMMON,
Holger Hans Peter Freyther <=