Replies: 2 comments 4 replies
-
|
This could be done by ditching hyperfine and just use the time command in a loop. I will look into this. |
Beta Was this translation helpful? Give feedback.
-
|
Done: https://github.com/jinyus/related_post_gen#memory-usage-results |
Beta Was this translation helpful? Give feedback.
-
|
Thank you! Very useful, because when you run out or RAM, performance tanks or you get a crash. F# (AOT), while relatively fast, uses 1 GB for 60k posts. That's about 10x more than Rust. Scala native 4 GB for 60k posts. While Zig uses 30 MB. Ouch. |
Beta Was this translation helpful? Give feedback.
-
|
Yea, I was surprised by those 2 as they are my favorite Langs, though json might be influencing this number. I will try manually parsing to see if that could be the issue. |
Beta Was this translation helpful? Give feedback.
-
|
After doing some tests, I think I will have to remove the chart as the numbers are heavily skewed by json encoding/decoding and the solutions weren't optimized for that, so it's misleading. |
Beta Was this translation helpful? Give feedback.
-
|
Measuring memory consumption is hard. What if that chart is collapsed by default, and you add a warning that the numbers are heavily skewed by json encoding/decoding? |
Beta Was this translation helpful? Give feedback.
-
Memory consumption is important factor, but often missing in benchmarks.
Beta Was this translation helpful? Give feedback.
All reactions