I'm working on a Javascript widget library and desperately looking for performance issues. It does some things asynchronously and interleaved in reaction to some events (just GUI events, no network stuff). I suspect this interleaving to be much deeper (which would be a bug) than I expect, but I can't really find out details. I'm also not sure if that is the actual reason or if it is something entirely different.
For example, in http://ift.tt/2hbMXK7, you will find a sample application, which reacts really slooow in some situations. For example, selecting a leaf in the tree will rebuild some parts of the UI, which takes way too long.
When I use e.g. the Chrome profiler, I actually see some suspicious artifacts, which should be different, but not really the root cause. I think this could be easier with something like an 'asynchronous callstack'.
Is there some kind of trick, programming pattern or any other helpful hint for analyzing such kinds of performance issues in web applications? Maybe I'm just trapped in the XY problem with the async callstack thing?!
Aucun commentaire:
Enregistrer un commentaire