the best and worst run may be the most important runs. the worst run in particular. you may have code that usually runs well, but might have bad worst case performance.
depending on how your code is used, the biggest improvement may come from improving the worst-case performance. On Wed, Aug 22, 2012 at 4:40 PM, Alan Gutierrez <a...@prettyrobots.com> wrote: > I'm starting to use `node-bench` to benchmark a packet parsing library, binary > to JSON conversion and vice-versa. > > I'm wondering if, when you create your benchmarks, how do you account for > garbage collection? Has anyone written some nice libraries or gists that would > help get better results out of `node-bench` like throwing away the best and > worst run? (Found `visualbench` and plan on using it.) > > -- > Alan Gutierrez - http://twitter.com/bigeasy > > -- > Job Board: http://jobs.nodejs.org/ > Posting guidelines: > https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines > You received this message because you are subscribed to the Google > Groups "nodejs" group. > To post to this group, send email to nodejs@googlegroups.com > To unsubscribe from this group, send email to > nodejs+unsubscr...@googlegroups.com > For more options, visit this group at > http://groups.google.com/group/nodejs?hl=en?hl=en -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups "nodejs" group. To post to this group, send email to nodejs@googlegroups.com To unsubscribe from this group, send email to nodejs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
