HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
MagicStack
vmbench
Python2016–2016
MagicStack / vmbench

vmbench

Network Server Performance Benchmarking Toolbench

3Distinct people
5Mentions
0Explicit recommenders
189GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Network Server Performance Benchmarking Toolbench

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 6:01:08 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by hour5 dated mentions

Observed mentions: 2016-05-04 03:32:41 UTC to 2016-05-04 14:24:22 UTC.

012016-05-04 03:00:00 UTC to 2016-05-04 04:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsMay 4, 03:002016-05-04 04:00:00 UTC to 2016-05-04 05:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2016-05-04 05:00:00 UTC to 2016-05-04 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-05-04 06:00:00 UTC to 2016-05-04 07:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2016-05-04 07:00:00 UTC to 2016-05-04 08:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2016-05-04 08:00:00 UTC to 2016-05-04 09:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsMay 4, 08:002016-05-04 09:00:00 UTC to 2016-05-04 10:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-05-04 10:00:00 UTC to 2016-05-04 11:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-05-04 11:00:00 UTC to 2016-05-04 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-05-04 12:00:00 UTC to 2016-05-04 13:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-05-04 13:00:00 UTC to 2016-05-04 14:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-05-04 14:00:00 UTC to 2016-05-04 15:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsMay 4, 14:00

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
May 4, 03:002016-05-04 03:00:00 UTC2016-05-04 04:00:00 UTC101
May 4, 04:002016-05-04 04:00:00 UTC2016-05-04 05:00:00 UTC101
May 4, 05:002016-05-04 05:00:00 UTC2016-05-04 06:00:00 UTC000
May 4, 06:002016-05-04 06:00:00 UTC2016-05-04 07:00:00 UTC101
May 4, 07:002016-05-04 07:00:00 UTC2016-05-04 08:00:00 UTC101
May 4, 08:002016-05-04 08:00:00 UTC2016-05-04 09:00:00 UTC000
May 4, 09:002016-05-04 09:00:00 UTC2016-05-04 10:00:00 UTC000
May 4, 10:002016-05-04 10:00:00 UTC2016-05-04 11:00:00 UTC000
May 4, 11:002016-05-04 11:00:00 UTC2016-05-04 12:00:00 UTC000
May 4, 12:002016-05-04 12:00:00 UTC2016-05-04 13:00:00 UTC000
May 4, 13:002016-05-04 13:00:00 UTC2016-05-04 14:00:00 UTC000
May 4, 14:002016-05-04 14:00:00 UTC2016-05-04 15:00:00 UTC101

What Hacker News says

1 sources
The benchmarks for node.js are terribly misleading. The node.js implementations only ever spawn a single process, and thus node is only running on a single core and uses only a single thread. Specifically, the http server example(1), doesn't even bother using the standard library provided Cluster module(2). Cluster is specifically designed for distributing server workloads across multiple cores. All node.js services/applications I've worked on in the past 3 years (that are concerned with scale) utilize a multi-process node architecture. The current benchmark can only claim that a single python process that spawns multiple threads is 2x faster than a single node.js process that spawns only one thread. This fact may be interesting to some, but is irrelevant to real world performance. [1]: https://github.com/MagicStack/vmbench/blob/master/se
Read the rest
In Uvloop: Fast Python networking

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.