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

Tree: d5e911c51e

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
Timothy J Fontaine	bfc823de90	benchmark: update to use new wrk	11 years ago
Fedor Indutny	f2d5cea73a	benchmark: add chunked-encoding benchmark	12 years ago
isaacs	d62cf59dc1	http: Don't hot-path end() for large buffers The benefits of the hot-path optimization below start to fall off when the buffer size gets up near 128KB, because the cost of the copy is more than the cost of the extra write() call. Switch to the write/end method at that point. Heuristics and magic numbers are awful, but slow http responses are worse. Fix #4975	12 years ago