A question appeared on the ExtJS forums today regarding how to bind event listeners on multiple links that are generated from the server. Bind an event listener to each link, right? Wrong! This is wrong in the sense that it wastes system resources and is unnecessary. Can you imagine how much resources TreePanel would take up if it bound a click listener on every single node element!? Oh wait… that’s probably what you though it did :-). But it doesn’t.
In our application at ControlPath, we have a pretty complex permission system. Well, imagine a permission system based off of a cyclical graph of 30,000 nodes with multiple levels of inheritance rules and you just begin to scratch the surface. I recently rewrote the permission rebuild caching system into recursive stored procedures. This improved performance from 45 minutes… to 45 seconds. There are a bunch of tricks I employed to get this kind of speedup, but today I am going to share 2 of the simplest ones with you… Continue reading
Fairly recently, I did some performance tuning on our MySQL servers and discovered some very interesting things. The previous “DBA” had the mantra of “set the value higher and it will go faster.” We are running some pretty beefy hardware so I can definitely see where this logic would come in to play. I became concerned when my little laptop with a default MySQL installation was getting better performance than our 8 gig of Ram, dual processor quad core monster server.
Its a pretty simple code snippet but the overarching topic, performance (especially in ExtJS), can be complicated and developers really need to be cognizant of performance impacts. Especially so when its running on the client which you have no control over the performance specs of the machine.
There has long been the problem in Ext with the issue of cleaning up event listeners after the listening component has been destroyed. Until now, developers have had to code custom destructors to handle this cleanup.