F# for Performance-Critical Code, by Matthew Crews

[@havokgames8297]

I can't imagine seeing something is 10's of millions times too slow and thinking "we can get there"

[@WonderfulPlays]

I agree with Khalid, I was rooting alongside the talk! And what a great one it was, Matthew you really have a talent for presenting!

[@FastFSharp]

Thank you! That is very kind 😊

[@10199able]

One of the greatest talks I have ever been

[@octoplasma2]

This is the talk I needed! Awesome! Thanks Matt!

[@FastFSharp]

My pleasure! Feel free to reach out if you ever have questions.

[@ARVash]

Awesome talk! I'm really excited about trying to apply these ideas.

[@daviidon]

Very inciteful, the last "hack" is both awesome and scary.

[@FastFSharp]

It is definitely reserved for extreme scenarios 😊

[@mumk]

absolutely mindblowing, what a phenomenal journey for that sweet 100x performance improve, you are a great engineer, I am inspired, cheers

[@codewithkv]

Great talk! I had no idea you could get that kind of performance out of F#.

[@HAMYLABS]

Great talk! F# FTW

[@danielmarbach3235]

Super geeky but still very approachable! Well done

[@FastFSharp]

Thank you! My hope was that it would be approachable.

[@NickMaovich]

nice talk! Matthew the F# legend

[@Madison-mk8ce]

love the way you talk about the language. To the point but understandable

[@rade6063]

This is such a great talk

[@FastFSharp]

Thank you for the kind words!

[@JasonCone]

Great talk. Thanks!

[@F.a797]

Such as a good talk

[@winstonsmith1977]

Great talk! Why there are so few f# jobs out there? Would love to switch from c#.

[@ABW5662]

fantastic talk. thank you

[@obilykua]

Great presentation!

[@warrenhenning8064]

AWESOME

[@FastFSharp]

Glad you liked it!

[@domenichelfenstein6584]

Awesome talk!

[@FastFSharp]

Thank you!

[@BentRasmussen]

Amazing!

[@DaveYostCom]

Great talk! The chart at 43:59 - could you make this available as log scale? That would make it easier to compare the various changes. The linear y axis misleadingly emphasizes the latest of the fixes, whereas a log y axis may show that other, earlier fixes are more powerful.

[@FastFSharp]

Doesn't really help me but here you go: drive.google.com/file/d/1lUEdkz4XqvDnJJXFTCtq5cE0WyvK8mB7/view?usp=drivesdk

[@DaveYostCom]

@@FastFSharp Thanks! The linear chart does misleadingly emphasize the latest of the fixes, whereas the log chart clearly shows that the most important fix was the first one, to use mutable. (I would set the lower end of the y axis to 10,000 to make it easier to see the relative benefits of each fix.)

[@FastFSharp]

@@DaveYostCom Glad you found it useful 😊

[@DaveYostCom]

What happened to the logarithmic plot? Didn’t you post it here?

[@ks1970in]

just wondering, can it be faster still ?

[@nalcij]

It runs off dotnet, It’s not blazingly fast but it's not slow either. Think of it like C#.

[@L0wPressure]

My man, it's all awesome, and you are doing a great job but i really don't see any benefits in using F# if you go down to such optimizations in the end. Why not use Rust instead?

[@zombie_pigdragon]

Because, as said in the beginning (1:42), this is a dotnet shop. Training developers in a new language/ecosystem is prohibitively expensive. That said, at this kind of speed, moving the optimized algorithms/data structures to Rust/C++ would be a possible next step for going even faster by enabling the addition of even more micro-optimisations in the hot code, if the speed that the F# reaches was somehow still not fast enough.

[@L0wPressure]

@@zombie_pigdragon it’s not about the goals of a workshop, but rather the goals of the developer. As far as I remember he wrote it for his work project, not for the workshop, and what I ask is - why this exact language? It’s seems like it was not made for this exact job. That’s all, otherwise great video.

[@zombie_pigdragon]

@@L0wPressure Sorry, I used "shop" to refer to his place of work. The place that he works uses dotnet exclusively. I do agree though that F# isn't made for hyper-optimized code, but the talk is demonstrating the exact opposite.

[@L0wPressure]

@@zombie_pigdragon got it, so i misread you initially.

[@aguluman]

Indeed, we need suffering and pain to live a meaningful life. #bigthink. This must have been difficult.