Comments on: Javascript optimization – high performance JS apps

By: The art and science of performant Web 2.0 AJAX apps « Fluent.Interface

The art and science of performant Web 2.0 AJAX apps « Fluent.Interface — Mon, 09 Jun 2008 14:24:56 +0000

[...] JS libraries such as Prototype, JQuery etc. it can be easy to forget how expensive repeated DOM calls [...]

By: Javascript optimization | Fomly

Javascript optimization | Fomly — Tue, 27 May 2008 13:02:15 +0000

[...] Link:Javascript optimization – high performance JS apps [...]

By: lillbra » Blog Archive » Tänkvärda tips om prestanda

lillbra » Blog Archive » Tänkvärda tips om prestanda — Tue, 27 May 2008 05:25:39 +0000

[...] Schellenbach listar prestandatips för javascript i artikeln Javascript optimization – high performance JS apps (via Ajaxian). För snabbare javascript bör man bland annat tänka på [...]

By: Prototype Javascript optimization to get best performance at AjaxApp.com, ajax app and cool web app!

Thu, 22 May 2008 12:12:07 +0000

[...] tips and those “NOT SUPPOSED TO DO” have been given by Thierry Schellenbach as listed below after he’s played with the functions console.profile() / console.profileEnd() [...]

By: Die goldenen Regeln für schnelle Prototype-Anwendungen | Ajaxschmiede.de

Die goldenen Regeln für schnelle Prototype-Anwendungen | Ajaxschmiede.de — Wed, 21 May 2008 23:14:18 +0000

[...] BWL-Student und Javascript-Programmierer Thierry Schellenbach veröffentliche in seinem Mellow-Morning-Blog eine Abhandlung über geschwindigkeitsoptimiertes Entwickeln von Prototype-Anwendungen. Als [...]

By: dtsn : Super Fast Prototype [javascript]

dtsn : Super Fast Prototype [javascript] — Wed, 21 May 2008 19:35:12 +0000

[...] If your a regular subscriber to my blog (and if you aren’t don’t forget you can subscribe here) you will know that I love Prototype, I was incredibly excited to see that Ajaxian had covered Thierry Schellenbach post about high performace JS apps. [...]

By: Jonah Dempcy

Jonah Dempcy — Wed, 21 May 2008 09:45:20 +0000

Is it true that using the each() method has a considerable negative impact on performance?

I did extensive performance testing and tuning of a JavaScript app using MooTools and we found a few performance bottlenecks, but nothing with the each() loops. When compared to conventional core DOM methods, the each() loops had a negligible difference in time spent.

Also, out of curiosity, what are you using for profiling?

By: Eiden

Eiden — Mon, 19 May 2008 15:12:25 +0000

The templates in Prototype are very slow!

This little mod gives it a good perforance-boost :)
http://no-cache.net/?p=6

By: tschellenbach

tschellenbach — Mon, 19 May 2008 15:10:46 +0000

Hey,

Yes that is indeed a very nice solution.
I referred to it with point 4:
Bind once to a common parent element.

I am still not sure whether i prefer that or the old school onclick approach.

Cheers,
Thierry

By: solnic

solnic — Mon, 19 May 2008 12:33:14 +0000

Hello,

Regarding “Remove Double Dollar $$ and event binding” I’d say it is much better to use event delegation instead of attaching event listeners to each element, this is even faster and requires less memory.

Cheers!

By: Ajaxian » Some more JavaScript performance tips

Ajaxian » Some more JavaScript performance tips — Mon, 19 May 2008 12:09:36 +0000

[...] Schellenbach has written up some thoughts about JavaScript optimization for Prototype apps after playing with console.profile() / console.profileEnd() in his Prototype [...]