1079630bd4
`make perf` will build, by default, perf.log, but you may also build perf.*; for example: $ make perf.1 # make some changes $ make perf.2 This allows comparing changes easily. |
||
---|---|---|
.. | ||
README | ||
common.js | ||
perf-class-define-methods-keyword-private.js | ||
perf-class-define-methods-keyword-protected.js | ||
perf-class-define-methods-keyword-public.js | ||
perf-class-define-methods.js | ||
perf-class-define-named.js | ||
perf-class-define-properties-keyword-private.js | ||
perf-class-define-properties-keyword-protected.js | ||
perf-class-define-properties-keyword-public.js | ||
perf-class-define-properties.js | ||
perf-class-define.js | ||
perf-class-get-property.js | ||
perf-class-inst-anon-empty.js | ||
perf-class-inst-named-empty.js | ||
perf-class-invoke-method.js | ||
perf-class-require.js | ||
perf-class-set-property.js | ||
perf-trait-define.js | ||
perf-trait-invoke-method.js | ||
perf-trait-methods.js | ||
perf-trait-mixin.js | ||
runner.in |
README
This directory contains the performance tests. These tests contain basic routines that perform a single action and output the result in seconds, with a basic description of what has been done. The timing is done via the native Date object to ensure that it can be run both server and client-side. It is important that each test performs only a single operation to ensure that the prior operations have no consequences on the previous, at least when run server-side by invoking a separate executable for each.