PEpedro93·Jul 18, 2014
It's a binding library of r3, you may check the benchmark from r3 project:
https://github.com/c9s/r3#performance
In R3 bindings for Node.jsc9s
r3
C2014–2014
c9s / r3
r3
libr3 is a high-performance path dispatching library. It compiles your route paths into a prefix tree (trie). By using the constructed prefix trie in the start-up time, you may dispatch your routes with efficiency
2Distinct people
3Mentions
0Explicit recommenders
822GitHub stars
What to know before exploring
What it is
libr3 is a high-performance path dispatching library. It compiles your route paths into a prefix tree (trie). By using the constructed prefix trie in the start-up time, you may dispatch your routes with efficiency
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, 3:56:07 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 week3 dated mentions
Observed mentions: 2014-05-18 00:36:27 UTC to 2014-07-18 11:53:08 UTC. Weeks start Monday, UTC.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| May 12 | 2014-05-12 00:00:00 UTC | 2014-05-19 00:00:00 UTC | 2 | 1 | 1 |
| May 19 | 2014-05-19 00:00:00 UTC | 2014-05-26 00:00:00 UTC | 0 | 0 | 0 |
| May 26 | 2014-05-26 00:00:00 UTC | 2014-06-02 00:00:00 UTC | 0 | 0 | 0 |
| Jun 2 | 2014-06-02 00:00:00 UTC | 2014-06-09 00:00:00 UTC | 0 | 0 | 0 |
| Jun 9 | 2014-06-09 00:00:00 UTC | 2014-06-16 00:00:00 UTC | 0 | 0 | 0 |
| Jun 16 | 2014-06-16 00:00:00 UTC | 2014-06-23 00:00:00 UTC | 0 | 0 | 0 |
| Jun 23 | 2014-06-23 00:00:00 UTC | 2014-06-30 00:00:00 UTC | 0 | 0 | 0 |
| Jun 30 | 2014-06-30 00:00:00 UTC | 2014-07-07 00:00:00 UTC | 0 | 0 | 0 |
| Jul 7 | 2014-07-07 00:00:00 UTC | 2014-07-14 00:00:00 UTC | 0 | 0 | 0 |
| Jul 14 | 2014-07-14 00:00:00 UTC | 2014-07-21 00:00:00 UTC | 1 | 0 | 1 |
What Hacker News says
3 sources(Pre-disclaimer: I think it's great that the author spent some time benchmarking and hacking, and I don't mean for this comment to tear down their work, but rather I'm just answering the above question which was also the first thing that came to my mind when I saw this.)
The slowest URL router benchmarked there[1] does 10462.0 runs per second, which is just under 0.1ms per run.
I'm not sure what performance is expected of Rails handlers but the first stackoverflow thread[2] that came up on a simple Google search had twitter doing 600 req/s across 180 instances which comes to 300ms per request.
By that math, the slowest URL router costs 0.033% of the request overhead.
Caveat: 300ms/req is slower than you'd like for an interactive website; real websites may have more complicated routing tables than this benchmark. Counter-caveat: 0.1ms is
Read the rest
not enough to matter pretty much anywhere except for the stock market.
[1]: https://github.com/c9s/r3#benchmark
[2]: http://stackoverflow.com/questions/373098/whats-the-average-...
R3 – High-performance URL router library in C
77 points · Open discussion