frozen VS tracy

I found this extension that implements "frozen" versions of some C++ containers, but I was wondering if there is a good solution available in the standard library.

A library exists that can produce constexpr hash table based containers.

I use the Frozen library for that. Since the conversions should be known at compile time you can make constexpr hash tables for lookups.

The constexpr dependency of note here is frozen.

In C++, a drop-in replacement for your DSA can provide significant improvements over the standard library. Particularly the standard unordered_map class can be improved by 50% to 100% (e.g. https://github.com/greg7mdp/parallel-hashmap, or for static maps https://github.com/serge-sans-paille/frozen). Of course, recognize that creating a DS/A from scratch is an entire project, and you shouldn't roll your own for an independent codebase.

Technologies (for curious folks): C++17, SFML, Entt, Frozen, Protobuf, spdlog, GoogleTest, GoogleBenchmark, CMake and Dear ImGui for debug purpose.

In the language, I added anonymous array literals. I did some cleanup in the compiler and updated to LLVM 12 from 10 (which was pretty trivial, surprisingly). I also added frozen, a C++ perfect-hashing library, as a dependency to speed up the lookup of keywords in my lexer. The library exploits C++’s constexpr features to generate a perfect hash at compile-time without any separate build step, which is great, and it also provides a drop-in replacement for std::unordered_map that uses the hash.

This is where I plug Frozen :-] https://github.com/serge-sans-paille/frozen

I’ve no idea how hard it is to implement, but return type polymorphism would be nice. Especially returning different things based on the constexpress of the result. And then add Frozen eqivalents of associative containers to the STL, so that, for example constexpr auto set = std::make_set(...) would be frozen::set, and auto set = std::make_set(...) would be std::set.

In which case, I believe the answer your question would be yes: the frozen map.

i don't really think there is _anything_ that comes even close to tracy https://github.com/wolfpld/tracy.

on top of this, given google's penchant for dumping projects aka abandonware, this would be an easy pass.

The RemedyBG debugger (https://remedybg.handmade.network/) and the Tracy profiler (https://github.com/wolfpld/tracy) both use Dear ImGui and so far I've only read high praise from people who used those tools compared to the 'established' alternatives.

For tools like this, programmers are also just "normal users", and from the developer side, I'm sure they evaluated various alternatives with all their pros and cons before settling for Dear ImGui.

Not the person you asked, but generally you might want to look at "frame-based" profilers. These are typically used in video games, but the concept is general, and can apply to other applications. The "frame" could also be something like a request or transaction being processed. I like Tracy[1], myself.

Another latency metric that you'll see, often w/respect to web apps and microservices is "P99" and similar. This is the amount of time in which 99% of requests get their response. For a higher percentile, you get a better idea of worst-case performance.

[1] https://github.com/wolfpld/tracy

I've not actually used Superluminal, but I use Tracy for similar reasons. It's free though (and, importantly, open source).

For profiling, you can check tracy.

You could try Tracy

There is no such thing as overengineering in fun projects, so I've also adopted Tracy as profiling solution. Works quite nice and gonna save me plenty of times in the future debugging performance spikes on badly optimized math heavy operations.

I know about tools such as tracing, jaeger or tracy. While having a complete tracing could be a potential solution, these tools don't work with no_std.