nkashyap
commented
10 years ago - SHA: 2b474e04390a0623b8beb4849ef8876e811003e0
- SHA: ae882480ac84357b955d67d9a364af643d84e34f
- SHA: 644cbd178d6f8ac129d7c4483385dad2428ad820
- SHA: a87372237d4ef9da7d2c341c69ddb0856a1d0bf1
- SHA: fdbe4f8d921e7efd058e379fbb3e08a220571aed
- SHA: 69f55b40d993fae3c47b73edf28c9c86d864f19a
- SHA: fcc74a7008c937e9681b453a5fd0f0720028f47f
- SHA: b1060ce9b27911532b0c8b5f7bf3de78a0d9a733
- SHA: 7031adada22740208976722e4c977e6edb1a2228
- SHA: ef28cd8139ddae6326d4c530eab8ca1ce397a101
From: Igor Bezkrovny
Hi,
We are working on SmartTV HTML5 games on wide range of TV platforms.
Profiling such games on device is only way to make games running fast. Profiling is must-have for development on SmartTV devices for us.
There are 2 methods to implement profiler in JS I see: 1) Project, that has been written in 8 hours in total: https://github.com/igor-bezkrovny/jsprofiler
I was inspired by deprecated yahoo profiler, but yui profiler very limited. So I used idea(such idea is used in john resig inheritance and stacktrace.js and so on) and implemented very useful profiler for SmartTV (JS). Please do not be angry on widget code - it is constantly under small improvements of information output.
Method: Walk recursively and instrument every found function and it's prototype. Minuses: a) anonymous function can't be instrumented automatically b) you should tell profiler which object/objects should be walked by profiler before html5 application start To instrument all global methods/classes/objects just use 'window' as root object
If you will be interested I have much more fresh and updated version (not published it yet).
2) Method: take AST(with Esprima for example), walk recursively, add call to small instrumentation utility methods before and after all functions and even to getters/setters and read-only properties, after that remove all original code in runtime, convert AST back to JS string (Esprima supports that) and eval all that code. We have all methods instrumented. Minuses: too complex implementation, possible unknown number of restrictions for eval'ing code on real projects, and memory consuming during instrumentation/ast generation/...
Also there is another model of profiling code, as it is done in chrome/firefox profilers. Difference between https://github.com/igor-bezkrovny/jsprofiler and chrome/firefox is that jsprofiler constantly updates and allows to profile dynamic problems in js games, it allows to see changes during game play without need to manual compare of snapshots of chrome's profilers every second.
It is very good idea to add profiler to console.io. What do you think?