Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Saved by the compiler: Parallelizing a loop with Rust and rayon

blog.faraday.io

Post reply on HN
Print view View original

11–20 of 33 posts

Re: Saved by the compiler: Parallelizing a loop with Rust and rayon

#11

Post by chrismorgan »

lmm wrote: post #6
jsingleton wrote: post #5

Your homepage crashed my browser. Not sure what you've got going on there. :/ Nice name but how does it relate to your product? I assume it refers to Michael Faraday. I have a bit of history about him and how he compares to Tesla, along with a tour of monuments to him in London here: https://unop.uk/faraday-tour

Maybe you should switch to a browser written in Rust.

Servo isn’t exactly hard to crash at present.

(“But hang on, it wasn’t supposed to crash!” I hear you saying. These are controlled, deliberate terminations due to detected logic errors, rather than crashes owing to memory unsafety issues like null pointer dereferencing.)

Re: Saved by the compiler: Parallelizing a loop with Rust and rayon

#12

Post by guildan »

ekidd wrote: post #9
jsingleton wrote: post #5

Your homepage crashed my browser. Not sure what you've got going on there. :/ Nice name but how does it relate to your product? I assume it refers to Michael Faraday. I have a bit of history about him and how he compares to Tesla, along with a tour of monuments to him in London here: https://unop.uk/faraday-tour

> Your homepage crashed my browser. Ouch. Sorry to hear that. What browser and version were you running? I'll file an issue. I asked our CEO where the name came from, and he said that Faraday is famous for being an experimentalist, which ties into our predictive modeling. (We also have lots of customers in the residential solar industry.)

I'm on Firefox 49.0.1 and the homepage did crashed mine too. When I visited the homepage, the bottom part was just a white space with nothing in it. Every other windows where unable to display their content anymore. (not the same guy as the first one who's browser crashed, but since my browser was not heavy customized I though would like to know).

Re: Saved by the compiler: Parallelizing a loop with Rust and rayon

#14

Post by jsingleton »

guildan wrote: post #12
ekidd wrote: post #9

Earlier quoted context omitted.

> Your homepage crashed my browser. Ouch. Sorry to hear that. What browser and version were you running? I'll file an issue. I asked our CEO where the name came from, and he said that Faraday is famous for being an experimentalist, which ties into our predictive modeling. (We also have lots of customers in the residential solar industry.)

I'm on Firefox 49.0.1 and the homepage did crashed mine too. When I visited the homepage, the bottom part was just a white space with nothing in it. Every other windows where unable to display their content anymore. (not the same guy as the first one who's browser crashed, but since my browser was not heavy customized I though would like to know).

I'm actually on Firefox 49.0.1 too. I just thought it was one of my add-ons or DNS hacks. Don't want to report a bug for an edge case but if others have the same issue it might be something more serious. Worked fine in Chrome.

Re: Saved by the compiler: Parallelizing a loop with Rust and rayon

#15

Post by ekidd »

guildan wrote: post #12
ekidd wrote: post #9

Earlier quoted context omitted.

> Your homepage crashed my browser. Ouch. Sorry to hear that. What browser and version were you running? I'll file an issue. I asked our CEO where the name came from, and he said that Faraday is famous for being an experimentalist, which ties into our predictive modeling. (We also have lots of customers in the residential solar industry.)

I'm on Firefox 49.0.1 and the homepage did crashed mine too. When I visited the homepage, the bottom part was just a white space with nothing in it. Every other windows where unable to display their content anymore. (not the same guy as the first one who's browser crashed, but since my browser was not heavy customized I though would like to know).

Thank you for confirming this problem! We've reproduced it internally and we're working on it.

Re: Saved by the compiler: Parallelizing a loop with Rust and rayon

#16

Post by masklinn »

jackmott wrote: post #3

A while back I did a whirlwind tour trying out different parallel looping abstractions in different languages, comparing their performance and ease of use. Rust+Rayon was one of the best. Simple code, fast runtime: https://jackmott.github.io/programming/2016/08/30/think-befo...

The first phrase is objectionable, the Pentium D was a (pretty badly implemented) reaction to AMD's announcement that they were going to bring their workstation and server dual-cores to the desktop. And while Intel technically did manage to take the crown the D was a pretty bad dual-core compared to the A64X2.

Re: Saved by the compiler: Parallelizing a loop with Rust and rayon

#17

Post by chrismorgan »

dkastner wrote: post #4
ekidd wrote: post #2

Author here. I'm happy to answer questions! I don't have any performance numbers for this loop because it was already very fast. This was just a warm-up exercise before trying to parallelize more complicated loops. My experience with Rust has been interesting. On the one hand, if you compare Rust to Ruby or JavaScript, there really is a "Rust tax"—you have to think about ownership and references and types. But Rust p…

A huge payoff that Rust provides vs Ruby or JavaScript is when writing development tools. It saves so much time and trouble to install a binary than to try and get someone to download the right version of Ruby, gem install, etc. Rust, while having its tax, is really great about telling you why your code won't compile and keeping you from footgunning yourself.

Trying to get ack or ag working properly on Windows is a bit of a pain. Now there’s an equivalent in Rust, rg, and I can get something that’s mostly superior to these others with `cargo install rg`. (OK, so I had to have installed Rust first. But I had done that.)

Re: Saved by the compiler: Parallelizing a loop with Rust and rayon

#18

Post by oldmanjay »

masklinn wrote: post #16
jackmott wrote: post #3

A while back I did a whirlwind tour trying out different parallel looping abstractions in different languages, comparing their performance and ease of use. Rust+Rayon was one of the best. Simple code, fast runtime: https://jackmott.github.io/programming/2016/08/30/think-befo...

The first phrase is objectionable, the Pentium D was a (pretty badly implemented) reaction to AMD's announcement that they were going to bring their workstation and server dual-cores to the desktop. And while Intel technically did manage to take the crown the D was a pretty bad dual-core compared to the A64X2.

From an editorial perspective that digression wouldn't have added a whole lot to the point of the page. What would you be hoping to communicate?

Re: Saved by the compiler: Parallelizing a loop with Rust and rayon

#19

Post by jackmott »

oldmanjay wrote: post #18
masklinn wrote: post #16

Earlier quoted context omitted.

The first phrase is objectionable, the Pentium D was a (pretty badly implemented) reaction to AMD's announcement that they were going to bring their workstation and server dual-cores to the desktop. And while Intel technically did manage to take the crown the D was a pretty bad dual-core compared to the A64X2.

From an editorial perspective that digression wouldn't have added a whole lot to the point of the page. What would you be hoping to communicate?

It might be slightly good to at least mention that AMD and Intel both worked on this at about the same time. I may make this edit next time I push an update for something else.

I welcome pedantic critiques because, well..I too am pedantic.

:D

Re: Saved by the compiler: Parallelizing a loop with Rust and rayon

#20

Post by masklinn »

oldmanjay wrote: post #18
masklinn wrote: post #16

Earlier quoted context omitted.

The first phrase is objectionable, the Pentium D was a (pretty badly implemented) reaction to AMD's announcement that they were going to bring their workstation and server dual-cores to the desktop. And while Intel technically did manage to take the crown the D was a pretty bad dual-core compared to the A64X2.

From an editorial perspective that digression wouldn't have added a whole lot to the point of the page. What would you be hoping to communicate?

> From an editorial perspective that digression wouldn't have added a whole lot to the point of the page.

Then remove it altogether and only talk in generalities? The rest of the paragraph doesn't namedrop specific brands.

Post reply on HN