Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

re-benchmark #72

Closed
tj opened this Issue Nov 6, 2012 · 6 comments

Comments

Projects
None yet
3 participants
Owner

tj commented Nov 6, 2012

with new master

Contributor

AlexeyKupershtokh commented Nov 10, 2012

also consider adding

setInterval(function() {
    console.log('Heap used: %dMB', Math.round(process.memoryUsage().heapUsed/1024/1024));
}, 1000);

in the benchmarks/pub.js

Contributor

AlexeyKupershtokh commented Nov 10, 2012

It's interesting what speed limit will not make the heap grow.

Collaborator

gjohnson commented Jan 1, 2013

pretty sure the benchmarks on the latest readme are up-to-date now. Close!

Owner

tj commented Jan 1, 2013

large byte ranges seem quite a bit worse, I'll update them with what I get right now and we can go from there

@tj tj closed this in 2464ae5 Jan 1, 2013

Owner

tj commented Jan 1, 2013

as much as big numbers are nice im probably going to lower the pertick rate anyway, it's not realistic, at most a production app would have maybe ~5-10 pertick

Collaborator

gjohnson commented Jan 1, 2013

Makes sense to me.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment