You are not logged in.
I wanted to see if a self compiled firefox is faster than the prebuild firefox.
Self compiled with make:
binary size = 49 kb
Self compiled with makepkg:
binary size = 62.8 kb
Prebuild firefox from pacman:
binary size = 64.3 kb
And the javascript benchmark of the makepkg and pacman version are ~30% slower than the make version.
Someone has an idea why the makepkg and make version arent the same size and speed?
PS: firefox version = firefox-9.0.1-1x86_64
-- If you need more info, tell me
, thanks in advance
Offline
How exactly did you measure this difference in speed? Seems like a huge difference there.
Offline
It's very simple: The abs build applies CFLAGS, CXXFLAGS and LDFLAGS from /etc/makepkg.conf. Your manual compile does not.
Though, that 30% difference looks suspect anyway, so yeah, how did you measure that?
Last edited by Gusar (2012-01-05 17:20:49)
Offline
firefox binary of that size won't include stuff that you would benchmark
make won't use CFLAGS/CXXFLAGS set in makepkg.conf
makepkg will
use the same and compare the size again
Offline
I am not home atm so ill check the size of the make version with the flags later.
The speed tests I did was:
http://www.webkit.org/perf/sunspider/sunspider.html
http://v8.googlecode.com/svn/data/bench … 6/run.html
-thanks for the replies btw-
EDIT: Sry for posting in "Pacman & Package Upgrade Issues" can someone transfer it to "Creating & Modifying Packages"?
Last edited by disparv (2012-01-05 18:16:34)
Offline
I'll stop being mysterious.
binary size = 49 kb <-- NOT F'ING POSSIBLE
Offline
I'll stop being mysterious.
binary size = 49 kb <-- NOT F'ING POSSIBLE
Of course it is. All the stuff is elsewhere, most of it in libxul.so and omni.jar. The firefox binary itself is extremely small.
Offline
bangkok_manouel wrote:I'll stop being mysterious.
binary size = 49 kb <-- NOT F'ING POSSIBLEOf course it is. All the stuff is elsewhere, most of it in libxul.so and omni.jar. The firefox binary itself is extremely small.
ok then back to my previous post, js benchmarks with this kind of binaries are pointless.
Offline
also:
http://www.archlinux.org/packages/extra/i686/firefox/
Package Size: 12.1 MB
Installed Size: 30.8 MB
Offline
@disparv
are you able to produce consistent results that you claim?
Offline
@bangkok_manouel: why is it pointless? And the size u show is not only the binary, its the full package.
@hadrons123: ye, the sunspider benchmark is ~12% faster, the V8 ~35%
But when im home again, ill do some more tests, i could have done something wrong.
Last edited by disparv (2012-01-05 18:52:55)
Offline
The thing is, CFLAGS certainly do noticeably affect js performance, it's very delicate code. It's the 30% difference that is odd to me, if it were around 10% it'd be believable. Also, sunspider is not really a good benchmark, and even v8 has it's quirks. It'd be cool to also test with kraken.
Last edited by Gusar (2012-01-05 18:53:47)
Offline
it's pointless because given the size the size of the binary, it does not include any js engine, just the UI at best. the "back" button I would say.
something is VERY wrong here.
Offline
The thing is, CFLAGS certainly do noticeably affect js performance, it's very delicate code. It's the 30% difference that is odd to me, if it were around 10% it'd be believable. Also, sunspider is not really a good benchmark, v8 is better. And it'd also be cool to test with kraken.
Ye ill do some more tests later.
@bangkok_manouel: any idea what the javascript binary is called?
Last edited by disparv (2012-01-05 18:57:31)
Offline
it's pointless because given the size the size of the binary, it does not include any js engine, just the UI at best. the "back" button I would say.
something is VERY wrong here.
Oh come on, no one is saying the size of the executable is affecting js performance. It's just one additional difference that can be observed when using different CFLAGS.
Offline
mod action
Sry for posting in "Pacman & Package Upgrade Issues" can someone transfer it to "Creating & Modifying Packages"?
Sure.
aur S & M :: forum rules :: Community Ethos
Resources for Women, POC, LGBT*, and allies
Offline
After some testing and recompiling, all 3 versions run almost at same speed.
--Thanks for the posts every1--
Offline
@ disparv
if there is a performance difference of this level why do we want to compile with CFLAGS?
is there a reliablity factor involved here?
Offline
@ disparv
if there is a performance difference of this level why do we want to compile with CFLAGS?
is there a reliablity factor involved here?
After some testing i didn't find a big performance difference.
Only difference i found was the binary size that ran from 49kb to 260kb.
Offline
if there is a performance difference of this level why do we want to compile with CFLAGS?
What you should do is compile with the flags that upstream has chosen (it's different flags for different components of firefox), this means unset CFLAGS and CXXFLAGS in the PKGBUILD. And you should use pgo. Pgo makes a big difference, on Windows up to 15%. Gcc isn't as good at pgo as msvc is, so the difference is a bit smaller on Linux.
Offline