I wish more ZK and FHE people would give their overhead as a ratio (time to compute in-cryptography vs time to compute raw), rather than just saying "we can do N ops per second" It's more hardware-independent, and it gives a very informative number: how much efficiency am I sacrificing by making my app cryptographic instead of trust-dependent? It's also often better for estimation because as a developer I *already know* how much time my computation takes to compute raw, so I can just multiply. (Yes, I know this is hard because the ops required are heterogeneous between executing and proving, especially around SIMD/parallelization and memory access patterns, so even a ratio is hardware-dependent to some extent, but even still I think overhead factor is a good number despite these imperfections)