Compile Stress Test
Published on , 1908 words, 7 minutes to read
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???
— snake enchantress (@AstraLuma) October 2, 2019
My wallet just cringed.
They have been now https://t.co/o5vMKx583C
— Cadey Ratio ๐ (@theprincessxena) October 2, 2019
— 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
— 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
— 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
— Cadey Ratio ๐ (@theprincessxena) October 3, 2019
me and my fiancรฉ: watch someone try to compile a 1.2 million line of code rust function over slack
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:
— Cadey Ratio ๐ (@theprincessxena) October 3, 2019
memcpy()!
01:01 (Cadey) dalias: this is basically 1.2 million instances of `printf("hello, world!\n");` in void main
— Cadey Ratio ๐ (@theprincessxena) October 3, 2019
01:01 (dalias) wtf
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"
— Cadey Ratio ๐ (@theprincessxena) October 3, 2019
"oh no"
"1.49"
"oh it stopped"
"it's definitely still in mir dataflow"
The memory is increasing
— Cadey Ratio ๐ (@theprincessxena) October 3, 2019
"what stage is that?"
— Jaden Weiss (@CompuJad) October 3, 2019
"denial?"
Lol it ran out of memory!
— Cadey Ratio ๐ (@theprincessxena) October 3, 2019
4 TB of ram isn't enough to build hello world in #rust!
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.
Facts and circumstances may have changed since publication. Please contact me before jumping to conclusions if something seems wrong or unclear.
Tags: rust