You can find the source for JSLitmus here. It has a great set of features and allows you to install it on your own site. So here are some pros and cons I found when setting up JSLitmus.
- Single-file install (JSLitmus.js)
- Works on Firefox, Opera, Safari, IE, Google Chrome, and iPhone browsers
- Adaptive test cycles – tests take ~1-2 seconds, regardless of the operation
- Google Chart + TinyUrl integration
- Open Source MIT-style license (see source)
- Need to host this on your own server.
- Need a place to save off/Manage existing Tests.
- Some tests report “Infinity” when run, which meant that the tests were executing so fast that it couldn’t get an accurate read on the total OPS/Sec.
JSLitmus is a nice set of tools. If you have access to your own host and are able to put together a way to manage the tests, I would recommend this is a possible solution. However, I did not go with this solution.
I found JSPerf.com after digging through the posts that Paul Irish’s put together about jQuery. 10 Things I Learned from the jQuery Source and 11 More Things I Learned from the jQuery Source. If you haven’t had a chance to read those, I highly recommend them, they help to give you a bit more information on whats going on in jQuery. They are also what lead me down the path to figure out why certain queries are slower than others, but thats another post all together.
- JSPerf is based on benchmark.js a very powerful performance testing suite.
- Has an online environment to store and test JS
- You can download the source and run it on your own host.
- You can browse through other peoples tests, make changes and save copies.
- You can see most popular tests
- Has quick links to embed common JS frameworks
- Browsing tests is a pain in the online tool
- Saving a copy of a test just adds a revision number to the end of the url rather than allowing you to create a new url for the test.
- Sometimes test runs aren’t saved off properly. I noticed this on my Mac using Safari 5.0.3
JSPerf seems to be able to handle all the aspects I need for everyday performance needs. I will be setting up a copy on this host, just so I can keep my own tests around and not need to bookmark them for reference later on.
Overall, I think JSPerf is the hands down winner at this point. Doesn’t mean I won’t find a better solution down the road, but for now, being able to quickly write a test on jsPerf and just run it to see how well it performs is much easier than hosting my own performance suite.
In the next couple of days I will be posting some of my performance test runs and some of the conclusions based on those results.