I am working Bug 595053 and Bug 620888 for 32-bit plugin support on 64-bit Firefox. Today, it is successful that 32-bit plugin (Flash and Sliverlight) runs on 64-bit Firefox.
This screenshot is sliverlight page on Firefox 64-bit (with 32-bit plugin support). Although Firefox process is 64-bit, sliverlight works.
This result of sunspider data is Firefox 4.0b9pre (2010-12-18) vs Google Chrome 10.0.612.1 dev on Ubuntu 10.10 + Intel Atom Z560. This result is interesting. (FROM is Chrome and TO is Firefox)
TEST COMPARISON FROM TO DETAILS
=============================================================================
** TOTAL **: 1.38x as fast 1361.8ms +/- 5.4% 987.8ms +/- 1.0% significant
=============================================================================
3d: 1.41x as fast 224.0ms +/- 11.6% 158.5ms +/- 0.9% significant
cube: ?? 61.7ms +/- 23.3% 64.0ms +/- 1.8% not conclusive: might be *1.037x as slow*
morph: 1.48x as fast 47.2ms +/- 8.7% 31.9ms +/- 3.1% significant
raytrace: 1.84x as fast 115.1ms +/- 9.3% 62.6ms +/- 1.1% significant
access: - 130.6ms +/- 12.0% 128.7ms +/- 2.5%
binary-trees: *2.02x as slow* 9.7ms +/- 42.8% 19.6ms +/- 12.8% significant
fannkuch: 1.42x as fast 53.3ms +/- 18.4% 37.6ms +/- 2.7% significant
nbody: 1.73x as fast 48.4ms +/- 11.9% 27.9ms +/- 2.2% significant
nsieve: *2.27x as slow* 19.2ms +/- 7.6% 43.6ms +/- 2.5% significant
bitops: 1.77x as fast 87.6ms +/- 19.7% 49.5ms +/- 4.9% significant
3bit-bits-in-byte: 2.79x as fast 7.8ms +/- 5.8% 2.8ms +/- 10.8% significant
bits-in-byte: ?? 17.8ms +/- 37.5% 19.6ms +/- 3.1% not conclusive: might be *1.101x as slow*
bitwise-and: 4.19x as fast 30.6ms +/- 22.5% 7.3ms +/- 6.6% significant
nsieve-bits: 1.59x as fast 31.4ms +/- 14.6% 19.8ms +/- 8.3% significant
controlflow: 1.49x as fast 12.7ms +/- 14.0% 8.5ms +/- 5.9% significant
recursive: 1.49x as fast 12.7ms +/- 14.0% 8.5ms +/- 5.9% significant
crypto: 1.65x as fast 111.6ms +/- 6.8% 67.6ms +/- 1.1% significant
aes: 1.61x as fast 59.7ms +/- 14.7% 37.1ms +/- 2.8% significant
md5: 1.64x as fast 26.0ms +/- 7.3% 15.9ms +/- 1.4% significant
sha1: 1.77x as fast 25.9ms +/- 7.1% 14.6ms +/- 3.4% significant
date: 1.50x as fast 241.3ms +/- 3.7% 161.3ms +/- 1.4% significant
format-tofte: *1.116x as slow* 84.7ms +/- 8.2% 94.5ms +/- 1.2% significant
format-xparb: 2.34x as fast 156.6ms +/- 4.6% 66.8ms +/- 4.2% significant
math: ?? 88.1ms +/- 4.4% 91.6ms +/- 1.3% not conclusive: might be *1.040x as slow*
cordic: *1.47x as slow* 19.4ms +/- 10.7% 28.5ms +/- 2.7% significant
partial-sums: 1.27x as fast 51.0ms +/- 5.3% 40.1ms +/- 1.0% significant
spectral-norm: *1.30x as slow* 17.7ms +/- 6.0% 23.0ms +/- 2.1% significant
regexp: 1.34x as fast 50.2ms +/- 8.4% 37.5ms +/- 7.6% significant
dna: 1.34x as fast 50.2ms +/- 8.4% 37.5ms +/- 7.6% significant
string: 1.46x as fast 415.7ms +/- 12.6% 284.6ms +/- 1.9% significant
base64: 1.44x as fast 30.2ms +/- 6.4% 21.0ms +/- 6.2% significant
fasta: 1.25x as fast 60.7ms +/- 5.1% 48.5ms +/- 2.6% significant
tagcloud: 1.31x as fast 114.1ms +/- 9.5% 87.2ms +/- 1.4% significant
unpack-code: 1.60x as fast 137.3ms +/- 22.0% 85.6ms +/- 2.5% significant
validate-input: 1.74x as fast 73.4ms +/- 20.7% 42.3ms +/- 6.5% significant
If you use Intel Core i7, this score is even. Why is V8 engine slow on Intel Atom?
Google Japan says, "グーグルがゼロからつくったブラウザ Google Chrome".
It means that "Google Chrome is written from scratch by Google.". Is it joke? They use WebKit redering engine and many open source codes such as libevent, libpng, libjpeg, nspr/nss and etc. Their behavior are a lack of respect for open source community. So I am very very sad...
This data is Firefox 4 x64 vs Internet Explorer 9 x64. Firefox 4 is three times faster than IE9。
TEST COMPARISON FROM TO DETAILS
=============================================================================
** TOTAL **: *2.90x as slow* 389.8ms +/- 3.0% 1132.2ms +/- 0.8% significant
=============================================================================
3d: *2.57x as slow* 71.7ms +/- 0.7% 184.0ms +/- 3.9% significant
cube: *1.94x as slow* 27.5ms +/- 1.4% 53.4ms +/- 1.8% significant
morph: *6.11x as slow* 11.0ms +/- 0.0% 67.2ms +/- 2.5% significant
raytrace: *1.91x as slow* 33.2ms +/- 0.9% 63.4ms +/- 9.6% significant
access: *4.97x as slow* 40.5ms +/- 18.4% 201.4ms +/- 1.0% significant
binary-trees: *2.81x as slow* 10.1ms +/- 71.9% 28.4ms +/- 3.4% significant
fannkuch: *4.72x as slow* 17.8ms +/- 1.7% 84.1ms +/- 0.3% significant
nbody: *11.0x as slow* 6.2ms +/- 4.9% 67.9ms +/- 1.3% significant
nsieve: *3.28x as slow* 6.4ms +/- 5.8% 21.0ms +/- 0.0% significant
bitops: *8.29x as slow* 18.9ms +/- 3.3% 156.7ms +/- 0.3% significant
3bit-bits-in-byte: *45.1x as slow* 0.8ms +/- 37.7% 36.1ms +/- 0.6% significant
bits-in-byte: *3.98x as slow* 10.3ms +/- 6.6% 41.0ms +/- 0.0% significant
bitwise-and: *23.3x as slow* 1.7ms +/- 20.3% 39.6ms +/- 0.9% significant
nsieve-bits: *6.56x as slow* 6.1ms +/- 3.7% 40.0ms +/- 0.0% significant
controlflow: *8.30x as slow* 4.7ms +/- 7.3% 39.0ms +/- 0.0% significant
recursive: *8.30x as slow* 4.7ms +/- 7.3% 39.0ms +/- 0.0% significant
crypto: *3.04x as slow* 35.4ms +/- 21.1% 107.5ms +/- 0.7% significant
aes: *1.62x as slow* 21.9ms +/- 33.5% 35.4ms +/- 2.0% significant
md5: *3.65x as slow* 9.6ms +/- 3.8% 35.0ms +/- 0.0% significant
sha1: *9.51x as slow* 3.9ms +/- 5.8% 37.1ms +/- 0.6% significant
date: *1.37x as slow* 58.0ms +/- 19.3% 79.7ms +/- 0.6% significant
format-tofte: *1.62x as slow* 27.4ms +/- 1.3% 44.5ms +/- 0.8% significant
format-xparb: ?? 30.6ms +/- 36.1% 35.2ms +/- 0.9% not conclusive: might be *1.150x as slow*
math: *3.46x as slow* 31.8ms +/- 1.4% 109.9ms +/- 0.9% significant
cordic: 1.28x as fast 13.4ms +/- 3.7% 10.5ms +/- 3.6% significant
partial-sums: *6.56x as slow* 9.0ms +/- 0.0% 59.0ms +/- 1.0% significant
spectral-norm: *4.30x as slow* 9.4ms +/- 3.9% 40.4ms +/- 1.2% significant
regexp: *2.24x as slow* 13.8ms +/- 4.1% 30.9ms +/- 2.3% significant
dna: *2.24x as slow* 13.8ms +/- 4.1% 30.9ms +/- 2.3% significant
string: *1.94x as slow* 115.0ms +/- 11.6% 223.1ms +/- 0.4% significant
base64: *6.18x as slow* 4.4ms +/- 8.4% 27.2ms +/- 1.1% significant
fasta: *2.06x as slow* 23.5ms +/- 31.5% 48.5ms +/- 1.4% significant
tagcloud: *1.99x as slow* 29.1ms +/- 25.9% 57.9ms +/- 0.4% significant
unpack-code: ?? 46.6ms +/- 21.0% 49.8ms +/- 1.1% not conclusive: might be *1.069x as slow*
validate-input: *3.48x as slow* 11.4ms +/- 76.3% 39.7ms +/- 0.9% significant
Armen announced Windows x64 build available on nightly build.
Also...
If you found new problem, please file a bug to bugzilla!
Thunderbird 3 or later uses SQLite3 to index mail body for "Gloda" full-text search. Gloda uses custom tokenizer "mozporter" to support non-ASCII characters. So when you open global-messages-db.sqlite, you cannot view a data into some tables such as messageText.
There is the way to view messageText table for command line version of SQLite3.
Before you try this, you should backup your database file!
sqlite> select hex(fts3_tokenizer('porter'));
00EF420A8C7F0000
sqlite> select fts3_tokenizer('mozporter',X'00EF420A8C7F0000');Then, you can view a data into messageText using SQL.
I posted an article to Japanese Mozilla community site about js-ctypes on Firefox.next (3.7). Firefox.next improves many features such as struct support and callback support for js-ctypes.
This is a sample to use color picker on Windows using js-ctypes. ComDlg32 has color picker API "ChooseColor()". This sample is to access ChooseColor().
Components.utils.import("resource://gre/modules/ctypes.jsm");
var custColors_type = ctypes.ArrayType(ctypes.int32_t, 16);
const CHOOSECOLOR = new ctypes.StructType(
'CHOOSECOLOR',
[
{'lStructSize': ctypes.uint32_t},
{'hwndOwner' : ctypes.uint32_t},
{'hInstance' : ctypes.uint32_t},
{'rgbResult' : ctypes.uint32_t},
{'lpCustColors' : custColors_type.ptr},
{'Flags' : ctypes.uint32_t},
{'lCustData' : ctypes.uint32_t},
{'lpfnHook' : ctypes.uint32_t},
{'lpTemplateName' : ctypes.uint32_t}
]);
var comdlg32 = ctypes.open("comdlg32");
var ChooseColor = comdlg32.declare("ChooseColorW",
ctypes.stdcall_abi,
ctypes.int32_t,
CHOOSECOLOR.ptr);
var custColors = new custColors_type();
var col = new CHOOSECOLOR (CHOOSECOLOR.size, 0, 0, 0,
custColors.address(), 0, 0, 0, 0);
ChooseColor(col.address());
alert(col.rgbResult);
You know, V8 by Google has the fastest JIT compiler. Many benchmarks get the top score on x86 environment. But how about on other CPU such as ARM? Any web sites don't research the benchmark on ARM.
I have a netbook using Freescale i.MX515. Although this net book "netwalker" is sold ($400?) at Japan market, I have tested Chromium 5.0 and Firefox 3.6 using Ubuntu 10.04 (lucid) beta. This data is on this environment.
This is interesting... V8 on ARM isn't optimized!. They should improve it for mobile market.
Nokia has a plan to discontinue Avkon (current S60 UI) as default widget. They will move to Qt that Nokia is their owner. For feature, I choose Qt as widget
As long as I look current port for mobile device such as Windows Mobile and Maemo, graphic performance is poor. Although currently device has Graphics acceleration, xulrunner uses software rendering. I think that this design is bad for mobile. Since mobile device is poor CPU performance, we should use GPU
Although RVCT 4.0 is free for Symbian developer, we cannot use for S60 now. S60 SDK only support RVCT 2.2 or GCCE (gcc 3.4). I want to use gcc 4.3 for Symbian build, but I have to modify SDK headers...
I have uploaded 64-bit version Firefox 3.6 RC1 to http://wiki.mozilla-x86-64.com/Firefox:Download.
Patch (Mercurial Queue format) will be uploaded to http://hg.mozilla-x86-64.com/hgwebdir.cgi/mozilla1.9.2-win64-mq/ at this week.
