Performance tests

[timdream]

lots of rooms of improvement possible

[timdream]

OK. Let's do this:

Create a grunt task that could run a performance test against a built database. For the test

1. Get the JSZhuyin running on node.
2. Prepare a set of symbol and character input, and feed it into the instance.
3. Measure the time it takes to complete.
4. Report N times it takes to complete & print it out with Node version etc.

In essence, the test is a lengthy version of the existing interactive/integration test.

[timdream]

PS Obviously the above plan only tests performance on V8. If we want to test performance on Gecko JS Engine (not sure about the current monkey name...), we should set up the same test case in a Firefox worker scope.

The point here is not to pollute the numbers with DOM performances, which can be vary greatly between browser versions and even on different graphic cards.

[timdream]

Here is what we should do to run the test in a browser, to get access other than V8.

• Running JSZhuyin inside a worker
• Run the commanding thread of JSZhuyin in a worker too
• DOM should only interact with the commanding thread.

The purpose of the test is to find performance bottlenecks, which running in a worker will give up enough clarity (and, with help like profilers in development tools). Unfortunately Gecko DevTools has no worker access yet though.

[timdream]

Fixed in 9f39f3593a09a101774e24fe26e75360140ce773.