User:GijsKruitbosch/JS Debugging/Profiling: Difference between revisions

m
Eradicate links to my old domain
(Adding profiling results and minor conclusions)
m (Eradicate links to my old domain)
 
Line 3: Line 3:
For the impatient:
For the impatient:


http://gijs.codingo.org/mozilla/soc/jprof2.html (790kb, fast machine, less data)
http://www.gijsk.com/mozilla/soc/jprof2.html (790kb, fast machine, less data)
http://gijs.codingo.org/mozilla/soc/jprof.html (1.7MB, slow machine, more data)
http://www.gijsk.com/mozilla/soc/jprof.html (1.7MB, slow machine, more data)




=== Main machine (fast) ===
=== Main machine (fast) ===
On a 3.4Ghz P4, 1GB of DDR2 RAM in Dual Channel, with lots of diskspace to spare, running Ubuntu Dapper and GNOME, Venkman took less than 3 seconds to start. The full profile can be found [http://gijs.codingo.org/mozilla/soc/jprof2.html here] (roughly 790kb html file). A summary of the top of the flat profile is as follows:
On a 3.4Ghz P4, 1GB of DDR2 RAM in Dual Channel, with lots of diskspace to spare, running Ubuntu Dapper and GNOME, Venkman took less than 3 seconds to start. The full profile can be found [http://www.gijsk.com/mozilla/soc/jprof2.html here] (roughly 790kb html file). A summary of the top of the flat profile is as follows:


<pre>68  5.1    js_LineNumberToPC
<pre>68  5.1    js_LineNumberToPC
Line 64: Line 64:


=== Laptop (slow) ===
=== Laptop (slow) ===
On a 850Mhz Celeron, 384MB RAM, running the same Ubuntu Dapper and GNOME, Venkman took slightly less than 20 seconds to start. The full profile can be found [http://gijs.codingo.org/mozilla/soc/jprof.html here] (warning: 1.7MB html file). A summary of the top of the flat profile is as follows:
On a 850Mhz Celeron, 384MB RAM, running the same Ubuntu Dapper and GNOME, Venkman took slightly less than 20 seconds to start. The full profile can be found [http://www.gijsk.com/mozilla/soc/jprof.html here] (warning: 1.7MB html file). A summary of the top of the flat profile is as follows:


<pre>359  4.9    js_Interpret
<pre>359  4.9    js_Interpret
Line 135: Line 135:
Filtering in Venkman/FE would be easier, though I'm wondering what the tradeoff between filtering in the backend compared to filtering in the front-end would be.
Filtering in Venkman/FE would be easier, though I'm wondering what the tradeoff between filtering in the backend compared to filtering in the front-end would be.


I think that's all for now - anyone reading this, feel free to direct comments to email, discussion page here, [http://gijs.codingo.org/blog/ comment on my blog], or {{bug|338978}}, etc.
I think that's all for now - anyone reading this, feel free to direct comments to email, discussion page here, [http://www.gijsk.com/blog/ comment on my blog], or {{bug|338978}}, etc.
Confirmed users
293

edits