Ben Noordhuis 8ae32a9864 bench: fix buffers/buffer-base64-encode benchmark ... The test is supposed to measure the performance of the base64 encoder so move the Buffer#write() calls out of the benchmark section. The overhead of the calls isn't terrible (about 1-3%) but having unrelated activity in a micro-benchmark is never a good idea. Signed-off-by: Trevor Norris <trev.norris@gmail.com>		2014-06-04 14:37:27 -07:00
..
buffer-base64-encode.js	bench: fix buffers/buffer-base64-encode benchmark	2014-06-04 14:37:27 -07:00
buffer-compare.js	buffer: add compare and equals methods	2014-04-28 22:09:48 -07:00
buffer-creation.js	bench: Consistency in benchmark filenames	2013-02-19 17:16:55 -08:00
buffer-read.js	buffer: improve {read,write}{U}Int* methods	2014-04-01 17:31:28 -07:00
buffer-slice.js	benchmark: Add a test to measure Buffer.slice perf	2014-05-28 11:57:05 -07:00
buffer-write.js	buffer: improve {read,write}{U}Int* methods	2014-04-01 17:31:28 -07:00
dataview-set.js	bench: Consistency in benchmark filenames	2013-02-19 17:16:55 -08:00