Like others have mentioned, in a CMS like project your bottlenecks are more likely in terms of database and/or caching. Span<T> , stackalloc and value-structs

Like others have mentioned, in a CMS like project your bottlenecks are more likely in terms of database and/or caching. Span<T> , stackalloc and value-structs will matter more when writing heavy data/number crunching scenarios like imageprocessing, games, "AI"/vector queries or things like _implementing_ database engines (see yesterdays discussion on the guys announcing they're using C++ where Rust, Go, Erlang, Java and C# was discussed for comparisons https://news.ycombinator.com/item?id=45389744 https://news.ycombinator.com/item?id=45389744 ). I'm often spending my days on writing applications that are reminiscent of CMS workloads and while I sometimes do structs, I've not really bought out my lowlevel optimization skills more than a few times in the past 6 years, 95% of the time it's bad usage of DB's.