3 ms·

So is /tmp a ramdisk? I have 64GB DDR4, but overclocked to double Infinity Fabric timings i.e. 3600 Mhz (it might be different for DDR5/ Zen4-5). I ran this on

by Ygg2 2y ago

So is /tmp a ramdisk? I have 64GB DDR4, but overclocked to double Infinity Fabric timings i.e. 3600 Mhz (it might be different for DDR5/ Zen4-5). I ran this on MSVC toolchain on windows. With like 43% memory taken by various Firefoxe and IntelliJ windows. Either compilers REALLY love CORES, or the Memory speed is causing issue :/ EDIT: Windows compilation 8min took less time than Linux 45min?

pytness 2y ago
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.
- Ygg2 2y ago
  > Try running `cargo build --timings`, it creates a report about build time Yeah, I got a bit longer time now, after `cargo clean `. Here are the timings: https://html-preview.github.io/?url=https://gist.githubusercontent.com/Ygg01/fb97a709b9bb88dfaaf428b8c111635e/raw/f4ffbc47a9cf16c421a0493732cf89128ffe5d99/veloren-win-perf-shot.html https://html-preview.github.io/?url=https://gist.githubuserc... It's still strange win 10 was faster to compile on a worse CPU and worse memory :/ Maybe WSL has some issues that MSVC toolchain doesn't. > I dont think i understood this correctly, but in the case you are asking (for clarification) about my compile times Yes. I was confused by its output, i.e. 2541.91s
  - pytness 2y ago
    > 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

by Ygg2 2y ago

pytness 2y ago

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.

Ygg2 2y ago
> Try running `cargo build --timings`, it creates a report about build time Yeah, I got a bit longer time now, after `cargo clean `. Here are the timings: https://html-preview.github.io/?url=https://gist.githubusercontent.com/Ygg01/fb97a709b9bb88dfaaf428b8c111635e/raw/f4ffbc47a9cf16c421a0493732cf89128ffe5d99/veloren-win-perf-shot.html https://html-preview.github.io/?url=https://gist.githubuserc... It's still strange win 10 was faster to compile on a worse CPU and worse memory :/ Maybe WSL has some issues that MSVC toolchain doesn't. > I dont think i understood this correctly, but in the case you are asking (for clarification) about my compile times Yes. I was confused by its output, i.e. 2541.91s
- pytness 2y ago
  > 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