..16-Mar-201612 KiB




CONTRIBUTING.md29-Dec-20123.3 KiB

COPYING29-Dec-201211.1 KiB

fonts/29-Dec-20124 KiB

README.md29-Dec-20123.8 KiB

robohornet.png29-Dec-20128.8 KiB

static/29-Dec-20124 KiB

vote.html29-Dec-20121.6 KiB

voting.py29-Dec-201210 KiB

1## Run the benchmark at [](
3## Learn how to [get involved](
5## RoboHornet Overview
7RoboHornet is predicated on a simple truth: if there's a popular benchmark, browser vendors will compete to win it. But up until today, benchmarks' power as a social tool has rarely been capitalized on. First of all, writing good benchmarks is hard. In practice, most benchmarks today were written by browser implementors to help them chart their performance — but the issues they picked aren't necessarily important to real web developers. Second, evangelizing a benchmark takes a lot of effort, and a benchmark is only as powerful as the social weight behind it. That's where RoboHornet comes in.
9**The goal of the RoboHornet benchmark is to distill the collective will of the web development community to get browser vendors to fix real-world performance pain points.** RoboHornet is an aspirational benchmark that sketches out a better future based on the performance pain of today.
15Why the name RoboHornet? Individual hornets, like web developers who evangelize for their pet performance problems, are annoying at best. But when they act as a part of a larger swarm, they can wield considerable power. And the "Robo" part? That should be self evident: robots are cool.
17Every benchmark in the suite is designed to capture a performance pain point in a measurable way, such that an improvement in the benchmark's speed represents a lessening of felt pain. Any performance pain point is fair game&mdash;not just the ones that involve JavaScript. The suite uses a [novel scoring system]( to represent the overall score as intuitively as possible. The community proposes performance painpoints to highlight and votes on which ones affect them most. A small group of stewards then distills the community's desires into regular, curated updates to the benchmark suite, allowing it to grow and evolve over time.
19Ultimately RoboHornet will be owned by the broader community. That's why we're open sourcing it in this **early alpha state**. The [list of stewards]( already includes representatives from many popular frameworks and applications, but ultimately RoboHornet isn't a coherent concept without the participation of the broader web community. Check out the [guide to community participation]( to get involved, or run the benchmark yourself at [](
23### Read more from the Wiki:
25*  <a href="/robohornet/robohornet/wiki/Adding-A-Benchmark">Adding A Benchmark</a>
26*  <a href="/robohornet/robohornet/wiki/Benchmark-Compatibility">Benchmark Compatibility</a>
27*  <a href="/robohornet/robohornet/wiki/Benchmark-Scoring">Benchmark Scoring</a>
28*  <a href="/robohornet/robohornet/wiki/Committee-Charter">Committee Charter</a>
29*  <a href="/robohornet/robohornet/wiki/Committee-Membership">Committee Membership</a>
30*  <a href="/robohornet/robohornet/wiki/Community-Participation">Community Participation</a>
31*  <a href="/robohornet/robohornet/wiki/FAQ">FAQ</a>
32*  <a href="/robohornet/robohornet/wiki">Home</a>
33*  <a href="/robohornet/robohornet/wiki/Issues-And-Benchmarks">Issues And Benchmarks</a>
34*  <a href="/robohornet/robohornet/wiki/Project-Organization">Project Organization</a>
35*  <a href="/robohornet/robohornet/wiki/Release-Process">Release Process</a>
36*  <a href="/robohornet/robohornet/wiki/Scoring-Rationale">Scoring Rationale</a>
37*  <a href="/robohornet/robohornet/wiki/Technical-Advisors">Technical Advisors</a>