lukechilds/node - node - Gitea: Git with a cup of tea

Author	SHA1	Message	Date
Rich Trott	c901741c60	benchmark: use strict mode Apply strict mode to benchmark code. PR-URL: https://github.com/nodejs/node/pull/5773 Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Myles Borins <myles.borins@gmail.com>	9 years ago
Rich Trott	6dc49ae203	tools,benchmark: increase lint compliance In the hopes of soon having the benchmark code linted, this change groups all the likely non-controversial lint-compliance changes such as indentation, semi-colon usage, and single-vs.-double quotation marks. Other lint rules may have subtle performance implications in the V8 currently shipped with Node.js. Those changes will require more careful review and will be in a separate change. PR-URL: https://github.com/nodejs/node/pull/5773 Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Myles Borins <myles.borins@gmail.com>	9 years ago
Rich Trott	ddac368533	benchmark: fix lint errors PR-URL: https://github.com/nodejs/node/pull/5773 Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Myles Borins <myles.borins@gmail.com>	9 years ago
Fedor Indutny	f5ab3e4c5c	benchmark: fixate `ciphers` in tls benchmarks Benchmark should always use the same cipher in order to be truthful.	11 years ago
isaacs	4b80f217cd	bench: Simplify duration arguments to benchmarks For throughput benchmarks, run with just 5s durations rather than 1s and 3s. For startup benchmark, run with just a single 1s duration, since it's very consistent anyway.	12 years ago
isaacs	0a406869df	bench: Replace tls-fragmentation with tls/throughput	12 years ago
isaacs	bafc51c0f9	bench: Move tls-connect into benchmark/tls Also, make it work properly with current node.	12 years ago