599239 - low frame rate while running chrome experiment monster

Status: RESOLVED DUPLICATE of bug 503470

(Core :: JavaScript Engine, defect)

Description

[Konstantin Novichikhin]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 6.1; en-GB; rv:1.9.2.10) Gecko/20100914 Firefox/3.6.10
Build Identifier: 4.0b7pre (f5c0015afe0e)

I was running comparison test between chrome and minefield. And minefield had very low frame rate while running the test. I

Reproducible: Always

Steps to Reproduce:
1. Go to http://www.chromeexperiments.com/detail/monster/
2. Launch experiment
Actual Results:  
Data gathered using oprofile: http://pastebin.mozilla.org/795746
The data was reset after the test was launched.


Build platform
target
i686-pc-linux-gnu

Build tools
Compiler
gcc
Version 
gcc version 4.4.1 [gcc-4_4-branch revision 150839] (SUSE Linux) 	
Compiler flags
-Wall -W -Wno-unused -Wpointer-arith -Wcast-align -W -pedantic -Wno-long-long -gstabs+ -fno-strict-aliasing -pthread -pipe -DDEBUG -D_DEBUG -DTRACING -g

Compiler
c++ 
Version
gcc version 4.4.1 [gcc-4_4-branch revision 150839] (SUSE Linux) 
Compiler flags
-fno-rtti -fno-exceptions -Wall -Wpointer-arith -Woverloaded-virtual -Wsynth -Wno-ctor-dtor-privacy -Wno-non-virtual-dtor -Wcast-align -Wno-invalid-offsetof -Wno-variadic-macros -Werror=return-type -pedantic -Wno-long-long -gstabs+ -fno-strict-aliasing -fshort-wchar -pthread -pipe -DDEBUG -D_DEBUG -DTRACING -g

Configure arguments
--enable-application=browser --enable-debug --disable-optimize

Comment 1

[Boris Zbarsky [:bzbarsky]]

Just to check, this is a build with JaegerMonkey enabled, right?

I'm pretty sure we have existing bugs about this demo in its non-chrome-experiment incarnation...

But in any case, looks about like this (all percentages are "under" unless they explicitly say "in"):

  20% in mjit-generated code
  20% Fill on the canvas
  10% NewInitObject + GC   9% painting
   5% SetName<0> (half is allocating slots and half is setting canvas styles)
   5% InitPropOrMethod
   4% stubs::CallName (mostly under NameOp getting call vars, looks like)
   3% array_join
   3% stubs::NewArray
   3% array_sort
   3% array_extra (mostly creating array objects)
   2% FillRect on canvas
   2% NewObject
   3% finalizer thread

Comment 2

[José Jeria]

This is a dupe of bug 503470

Comment 3

[Boris Zbarsky [:bzbarsky]]

Ah, indeed.