xesite/blog/compile-stress-test-2019-10-03.markdown

title	date	tags
Compile Stress Test	2019-10-03	rust

This is an experiment in blogging. I am going to be putting my tweets and select replies one after another without commentary.

shitty synthetic benchmark idea: how long it takes for a compiler to handle a main function with 1.2 million instances of printf("hello, world!\n") or similar

— Cadey Ratio 🌐 (@theprincessxena) October 2, 2019

fun fact, you need an AWS x1.16xlarge instance to compile 1.2 million lines of rust source code

— Cadey Ratio 🌐 (@theprincessxena) October 2, 2019

oh god that might not be enough

— Cadey Ratio 🌐 (@theprincessxena) October 2, 2019

oh god, is that what X1 is for???

My wallet just cringed.

— snake enchantress (@AstraLuma) October 2, 2019

They have been now https://t.co/o5vMKx583C

— Cadey Ratio 🌐 (@theprincessxena) October 2, 2019

pic.twitter.com/le8IFrFbQT

— Cadey Ratio 🌐 (@theprincessxena) October 2, 2019

TFW rust uses so much ram an x1.16xlarge can't compile hello world

— Cadey Ratio 🌐 (@theprincessxena) October 2, 2019

Let's go x1e.32xlarge!

— Cadey Ratio 🌐 (@theprincessxena) October 2, 2019

hello world

— Cadey Ratio 🌐 (@theprincessxena) October 2, 2019

Code generators

— Cadey Ratio 🌐 (@theprincessxena) October 2, 2019

pic.twitter.com/BwLhk9PIb3

— Cadey Ratio 🌐 (@theprincessxena) October 2, 2019

Rust can't match V for compile performance

— Cadey Ratio 🌐 (@theprincessxena) October 2, 2019

Finally can run two electron apps.

— Pradeep Gowda 🇮🇳🇺🇸 (@btbytes) October 2, 2019

pic.twitter.com/Ez0t5BLT9i

— Cadey Ratio 🌐 (@theprincessxena) October 2, 2019

It stopped growing at 2.66 TB of ram!

— Cadey Ratio 🌐 (@theprincessxena) October 2, 2019

overheard: "im paying this computer minimum wage to compile this god damn rust program"

— Cadey Ratio 🌐 (@theprincessxena) October 2, 2019

The guy who's paying for the instance in slack said it

— Cadey Ratio 🌐 (@theprincessxena) October 2, 2019

you magnificent cursed unholy monster

— Astrid 🦋 (@floofstrid) October 2, 2019

Just a simple rust program, only 9.88090622052428380708467040696522138519972064500917... × 10^361235 possible conditions

— Cadey Ratio 🌐 (@theprincessxena) October 2, 2019

oh god it's still going pic.twitter.com/SIZJBFTDHN

— Cadey Ratio 🌐 (@theprincessxena) October 3, 2019

Normal couples: watch tv together or something

me and my fiancé: watch someone try to compile a 1.2 million line of code rust function over slack

— Cadey Ratio 🌐 (@theprincessxena) October 3, 2019

I guess #rust isn't production-ready, it can't compile hello world.

— Cadey Ratio 🌐 (@theprincessxena) October 3, 2019

no swap used though pic.twitter.com/2Qb0pXqIme

— Cadey Ratio 🌐 (@theprincessxena) October 3, 2019

what the fuck is it doing pic.twitter.com/2CuVKhUAsF

— Cadey Ratio 🌐 (@theprincessxena) October 3, 2019

SURVEY SAYS:

memcpy()!

— Cadey Ratio 🌐 (@theprincessxena) October 3, 2019

01:01 (Cadey) dalias: this is basically 1.2 million instances of `printf("hello, world!\n");` in void main
01:01 (dalias) wtf

— Cadey Ratio 🌐 (@theprincessxena) October 3, 2019

AWS x1e.32large

— Cadey Ratio 🌐 (@theprincessxena) October 3, 2019

perf

— Cadey Ratio 🌐 (@theprincessxena) October 3, 2019

It's down to 1.36 TB now

— Cadey Ratio 🌐 (@theprincessxena) October 3, 2019

"back to 1.47T ram"
"oh no"
"1.49"
"oh it stopped"
"it's definitely still in mir dataflow"

— Cadey Ratio 🌐 (@theprincessxena) October 3, 2019

The memory is increasing

— Cadey Ratio 🌐 (@theprincessxena) October 3, 2019

"what stage is that?"
"denial?"

— Jaden Weiss (@CompuJad) October 3, 2019

Lol it ran out of memory!

4 TB of ram isn't enough to build hello world in #rust!

— Cadey Ratio 🌐 (@theprincessxena) October 3, 2019

Meanwhile the same thing in Go took 5 minutes and I was able to run it on my desktop instead of having to rent a server from AWS.