# Interesting Rust/web project - rework the compiler performance website

**URL:** <https://internals.rust-lang.org/t/interesting-rust-web-project-rework-the-compiler-performance-website/3124>\
**Category:** Uncategorized\
**Created:** [January 28, 2016, 4:04am UTC](https://internals.rust-lang.org/t/interesting-rust-web-project-rework-the-compiler-performance-website/3124 "2016-01-28T04:04:06Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![nrc](https://sea2.discourse-cdn.com/flex002/user_avatar/internals.rust-lang.org/nrc/32/126_2.png) [@nrc](https://internals.rust-lang.org/u/nrc)\
**Post date:** [January 28, 2016, 4:04am UTC](https://internals.rust-lang.org/t/interesting-rust-web-project-rework-the-compiler-performance-website/3124/1 "2016-01-28T04:04:06Z")

</div>

If anyone is looking for a project, this should be interesting and would be really useful for the Rust community. Last year I hacked up a system to track performance of the Rust compiler. You can see it [here](http://www.ncameron.org/perf-rustc/).

The ‘backend of the front end’ is a mess of node.js - [https://github.com/nrc/rustc-perf/blob/master/backend/perf.js](https://github.com/nrc/rustc-perf/blob/master/backend/perf.js) We’d like to extend what we can do, but before we do that, it would be nice to rewrite in Rust. Improving the frontend would be great too, but not as urgent or a Rust project. Is anyone keen?

---

<div class="post-metadata">

**Author:** ![jethrogb](https://avatars.discourse-cdn.com/v4/letter/j/43a26b/32.png) [@jethrogb](https://internals.rust-lang.org/u/jethrogb)\
**Post date:** [January 28, 2016, 11:48pm UTC](https://internals.rust-lang.org/t/interesting-rust-web-project-rework-the-compiler-performance-website/3124/2 "2016-01-28T23:48:53Z")

</div>

Might be better for users.r-l.o?

---

<div class="post-metadata">

**Author:** ![tamird](https://sea2.discourse-cdn.com/flex002/user_avatar/internals.rust-lang.org/tamird/32/14099_2.png) [@tamird](https://internals.rust-lang.org/u/tamird)\
**Post date:** [February 5, 2016, 2:44pm UTC](https://internals.rust-lang.org/t/interesting-rust-web-project-rework-the-compiler-performance-website/3124/3 "2016-02-05T14:44:47Z")

</div>

I’m interested in working on this.

Do you have any guidance on how to test it, when I have something working?

---

<div class="post-metadata">

**Author:** ![nrc](https://sea2.discourse-cdn.com/flex002/user_avatar/internals.rust-lang.org/nrc/32/126_2.png) [@nrc](https://internals.rust-lang.org/u/nrc)\
**Post date:** [February 8, 2016, 7:32pm UTC](https://internals.rust-lang.org/t/interesting-rust-web-project-rework-the-compiler-performance-website/3124/4 "2016-02-08T19:32:08Z")

</div>

@tamird - great! I’m afraid I don’t have much advice for testing. I would add a bunch of unit tests (which are currently missing). Beyond that, it should be possible to write system tests by setting up an HTTP client and sending API calls and testing the results are expected. You would need some known test data, rather than the live data (maybe even have a test repo to store data in so it is a full end to end test).

If you have any questions, you can ping me on irc.

---

<div class="post-metadata">

**Author:** ![nrc](https://sea2.discourse-cdn.com/flex002/user_avatar/internals.rust-lang.org/nrc/32/126_2.png) [@nrc](https://internals.rust-lang.org/u/nrc)\
**Post date:** [March 25, 2019, 8:25am UTC](https://internals.rust-lang.org/t/interesting-rust-web-project-rework-the-compiler-performance-website/3124/5 "2019-03-25T08:25:44Z")

</div>

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.