Projects tagged ‘javascript’ and ‘profiler’

For usage instructions, examples, and more, visit: http://www.gscottolson.com/blackbirdjs/

Firefox Profiler gives you the ability to analyze your Javascript code and determine bottlenecks. The idea is to output the data in the Callgrind format, and analyze it using KCacheGrind or WinCacheGrind.

This project aims to create a javascript profiler. The primary target is Internet Explorer, as several profilers already exist for Firefox (i.e. Firebug, Venkman). However, it is intended to support as many browsers as possible.

IntroductionThe Debug-JS project is designed to provide an easy, clean and clear way to debug JavaScript applications. This is a minimal-powerful implementation that's provides a set of debugging ... [More] , tracing and profiling tools designed using AOP. Debug-JS is easy. Why? It's object-oriented. It attaches to any object without adding dirty code into the application. It's compatible with several JS frameworks (see Compatibility page). It doesn't requires complex code implementation in order to be used. It's cross-browser compatible. Debug-JS is useful. Why? It has debugging, tracing and profiling support. It causes no overhead because uses only standard JavaScript. It could be used in any browser. It's lightweight, < 5KB packed and < 20KB the development version. It works all over a plugin architecture to extend and modify Debug-JS as needed. Good news!Now, you can use Maven to build Debug-JS! Using Maven is easier to make changes, create test cases and even new releases. You need to checkout the project first, from the following url: svn checkout http://debug-js.googlecode.com/svn/trunk/ debug-js-read-only And next you can use Maven in the project root directory: mvn clean install It will make a distribution including a site which allows to test Debug-JS in action. For more information, please see Setting up a Maven Environment in the wiki. Current ReleaseDebug-JS 0.11a (Galadriel) is ready for download!. For information about features in this version, please see the Release Notes How it works?Basic Debug-JS usage could be in three steps: 1. You should add the Debugger.js file to your HTML and initialize the framework. /* Include */ // Yes... it could be unattended, but you're free to choose :) Debugger.setup(); 2. You should create a Wrapper object and set the event handlers. /** * This handler will be called if any error occurs * inside the object that's being debugged. * * @param event {Debugger.DebugEvent} Event data. */ function errorHandler(event) { alert("Oops!, you became exceptional: " + event.data.error.message ); } var wrapper = new Debugger.Wrapper(errorHandler);3. You just need to attach the debugger to an object. var myObject = { foo : function() { // Error: Object 'bar' is undefined. alert(this.bar.foo); } }; myObject.debug(wrapper); myObject.foo(); // This call will throw an error.Now, every time that myObject throws an error in one of its methods (for example, when executes foo method), the errorHandler function will be notified. For information about different kind of handlers (tracing handler, profiling handler) please see the documentation. [Less]

Prototype ProfilerOverviewPrototype Profiler (pro2js) is a utility that can be used to detect poorly performing JavaScript code. In contrast to other profilers, pro2js supports all commonly used ... [More] browsers (including IE6). It allows you to work with test results easily and performance is excellent. Features:Prototype profiler is a "monkey patch" for the prototype library. It does not require modifications of the prototype code and it can be easily disabled (for example, in different environments). Prototype profiler logs all DOM–selectors and classifies them by selector type (for example: p#id7 ~ p -> element#id~element). Therefore, you can easily detect expensive DOM–selectors and avoid executing similar selectors multiple times. Prototype profiler will log the number of results returned by each of the selectors. This allows a user to find useless selectors or selectors which return an excessive number of results. Prototype profiler will also log all executed dom:load event handlers (dom:load event observers) and measure the speed at which they are executed in addition to displaying the list of selectors that were executed during the handler’s work. The utility is compatible with ie6+, FF, safari, opera, chrome, as well as with several mobile browsers (it was tested on iPhone and Nokia E-series). Usage exampleFirst of all, include pro2js lib right after the prototype library: Now you can create an instance of the profiler class and pass callbacks & options into it: var myDecoProfiler = new PrototypeProfiler({ 'onSelectorAdded': demoApp.updateSelectorsLog, 'onOnLoadEventAdded': demoApp.updateEventLog, 'namespace': 'demoApp' });And finally, define your callbacks: var demoApp = { updateSelectorsLog: function (profiler) { alert(Object.toJSON(profiler.selectors)); }, updateEventLog: function (profiler) { alert(Object.toJSON(profiler.events)); } };Below you can find examples of callback output: { "#id": [{ "query": "#events-log", "count": 0 }, { "query": "#events-log", "count": 0 }, { "query": "#events-log", "count": 0 }, { "query": "#sandbox", "count": 1 }] }[{ "name": "demoApp.sandbox.init()", "time": 20, "selectors": ["#sandbox", "#events-log"] }, { "name": "demoApp.selectorForm.init()", "time": 20, "selectors": ["#app", "form", "#anonymous_element_1", "#selector", "#events-log"] }, { "name": "function (e) {\n $(\"selector\").focus();\n}", "time": 16, "selectors": ["#selector", "#events-log"] }]Get more infoDownload pro2js and demo. Try live demo. Get the utility from the repository. View JSDoc documentation. Usersmydeco.com acunote If you use pro2js, please let me know so that I can add you to the list ThanksSpecial thanks to Mom and Dad, mydeco.com team, Paul Egan for his code review, Shane Evans for his help with docs and to Ilya Furman for beta-testing. [Less]