Yes, in linux there is a file system type called tmpfs which is mapped to memory (most of the time iirc).
> Filesystem Size Used Avail Use% Mounted on
> tmpfs 31G 22M 31G 1% /tmp
Try running `cargo build --timings`, it creates a report about build times.
My guess would be storage speed, i would not expect memory speed to be that much of an issue.
edit:
> Windows compilation 8min took less time than Linux 45min?
I dont think i understood this correctly, but in the case you are asking (for clarification) about my compile times, i got around 3m:18s on linux, and around >8 minutes on WSL.
> Yes. I was confused by its output, i.e. 2541.91s
Thats the output of the shell command `time` (im using zsh so the output differs from other shells) eg `time cargo build`.
system is the cpu time spent calling kernel functions
and user is the cpu time spent outside kernel functions.
The time is measured per core, so if the program runs for 2 seconds with 16 threads, the user time would be around 32.
Notice there is a cpu metric (1341% cpu), if you do:
(user + system) / cpu * 100 / 60 = ~3.29 minutes = 3m:17s
> Filesystem Size Used Avail Use% Mounted on
> tmpfs 31G 22M 31G 1% /tmp
Try running `cargo build --timings`, it creates a report about build times. My guess would be storage speed, i would not expect memory speed to be that much of an issue.
edit:
> Windows compilation 8min took less time than Linux 45min?
I dont think i understood this correctly, but in the case you are asking (for clarification) about my compile times, i got around 3m:18s on linux, and around >8 minutes on WSL.