I haven't own any macbook, but it seems "sysctl hw.cpufreq...." controls
frequency of the cpu.
I've repeat your test. I can do something wrong (I've got warning
message: "serializer 'java (externalizable)' failed round-trip test" +
scala + sbinary). And I've got different serialized size for thrift.
I've switched to protobuf-java-2.1.0, because the 2.0.2 library is
incompatible with 2.1.0 generated source (I won't use protobuf if they
make incompatible changes so often).
Here are results:
------------------------------------------------------------------------
Starting
Object create, Serialization, Deserialization, Total Time, SSize
thrift 930,47903, 7570,38250, 9062,38350, 17563,24503, 314
thrift 903,62937, 7662,11150, 8719,14350, 17284,88437, 314
thrift 891,74183, 7537,20100, 8809,45650, 17238,39933, 314
thrift 898,90696, 7605,01650, 9067,40050, 17571,32396, 314
thrift 904,09775, 7695,88850, 9237,59250, 17837,57875, 314
protobuf 1066,90265, 8909,92600, 5278,93150, 15255,76015, 217
protobuf 1042,76173, 8881,13450, 5313,92500, 15237,82123, 217
protobuf 1065,49403, 9196,53650, 5112,25400, 15374,28453, 217
protobuf 1047,32115, 8983,84900, 5092,27150, 15123,44165, 217
protobuf 1109,47716, 9291,45350, 5354,72300, 15755,65366, 217
------------------------------------------------------------------------
There isn't any major difference in serialization or deserialization
time. The difference between lowest and highest serialization (time?) is
just 2% for thrift and 4% for protobuf (deserialization: 5% for thrift
and protobuf).
------------------------------------------------------------------------
$ java -version
java version "1.6.0_0"
IcedTea6 1.3.1 (6b12-0ubuntu6.4) Runtime Environment (build 1.6.0_0-b12)
OpenJDK Client VM (build 1.6.0_0-b12, mixed mode, sharing)
Genuine Intel(R) CPU 2160 @ 1.80GHz (dual core)
Linux atlas 2.6.27-11-generic #1 SMP Thu Jan 29 19:24:39 UTC 2009 i686
------------------------------------------------------------------------
Should I change something in my setup?
В Птн, 15/05/2009 в 07:24 -0700, Chad Walters пишет:
> Given the fact that the deserialization time is basically constant, I
> am not sure this is the issue.
>
> This is on my MacBook Pro laptop, plugged in and with no particular
> special settings — if you know something I should enable/disable, let
> me know.
>
> Chad
>
> On 5/15/09 12:10 AM, "Alexander Shigin" <[email protected]> wrote:
>
> В Чтв, 14/05/2009 в 23:43 -0700, Chad Walters пишет:
> > I suspect it may have something to do with GC but haven't proved that
> > out yet. Notice that serialization time is highly variable but
> > deserialization time is almost constant.
> >
> > Any thoughts?
>
> Do you have any power-save technology enabled? I've come across some
> strange results when trying to do benchmarks with "cpufreq" enabled.
>
>
