Can Rust save the Planet? A Clickbait look at energy efficiency of Rust vs Node 

Thank you for the timestamps

@@masmullin No worries, if any are off let me know and I can tweak them.

Why not put this in the descripion instead, so RU-vid will add the timestamp sections to the video itself

I've followed your advice for the JS and have seen significant performance boost (nearly 20% improvement) on the users test. Will update with a follow up video in the next few days

Check out Vagelis channel ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-Vk41-xPxQI4.html Tl;dr php isn't in the same league

Not sure how to get json out of the sqlx rows other than handcrafting, or using serde_json on a user struct. hand crafting is not only worse code (more error prone), but also slower. That said, there are a few simple tweaks (instead of .collect(), pre-allocate the result vector, use row.get() instead of row.try_get) that can improve performance by 1% for the same 76.5W. Not enough to make me want to redo the video nor change my conclusion. There are more invasive performance boosts which can be done to the rust code (see previous video for possible techniques), but this handicaps the experiment as I am sure there are similar techniques to apply to javascript code which I am simply too novice in the language to apply. Optimizing Rust via: - mimalloc - thread_local! - single allocation the Json Buffer - use smallstr::SmallString instead of String for first_name and last_name Yields: 1692req/s (1.15x more req/s) with an energy usage of 74W for a milliwatt/req value of 43.7. CO2/Kg/Yearly = 1657.59 (down from 1972.37). Thus the usage of unoptimized node vs optimized Rust is 1.31x more CO2 emitted for the theoretical case of 10000 req/s requirement. So yeah, Rust can be further optimized. However, this is now comparing highly optimized rust code by an experienced Rust developer vs non-optimized node code written by an extremely junior developer.

@@masmullin "hand crafting is not only worse code (more error prone), but also slower." Why? directly writing the JSON String could avoid up to 2 allocations per user, which should improve it massively (well, if you don't use small string allocations already)

You’re welcome 😊

I misspoke when I was explaining my network speeds, I said "gigabyte" when I meant gigabit. Thus the 1580 is very close to the maximum transfer available on my network.