Benchmark server hot paths

[MCarlomagno]

We haven’t measured the server’s most expensive code paths yet. Once traffic ramps up, we’ll need data to decide where to optimize. Scope for later:

• Benchmark MidenNetworkClient::apply_delta and merge_deltas with realistic payload sizes to gauge serialization and replay-protection overhead under the global network-client mutex.
• Stress FilesystemService::pull_deltas_after with many delta files to see when directory scans/deserialization bottleneck get_delta APIs.
• Load test the canonicalization worker (mocked storage/network) to measure how many candidates/sec it can retire and whether the shared network-client lock becomes the bottleneck

[0x0Glitch]

Can i work upon this?

[MCarlomagno]

Hi @0x0Glitch thanks for the interest, for sure! Let me know if you need any assistance from my side.

Also I'm wondering your interest/use case for Private State Manager?

Thanks!

[0x0Glitch]

Hi @MCarlomagno, thanks for the quick response! No worries at all about prioritization — I totally understand, and I’m happy to hold on this until it fits your roadmap. If there are any smaller tasks or prep work I can help with in the meantime, I’d be glad to jump in.

…

On Sun, Dec 7, 2025 at 7:56 AM Marcos Carlomagno ***@***.***> wrote: *MCarlomagno* left a comment (OpenZeppelin/private-state-manager#59) <#59 (comment)> Hi @0x0Glitch <https://github.com/0x0Glitch> thanks for the interest, ATM we are prioritizing other work items, though we will be working on this soon. If there is a strong reason why you believe this should be prioritized, please let me know, Also I'm wondering your use case for Private State Manager? Thanks! — Reply to this email directly, view it on GitHub <#59 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BMIPLVM37KOSVA24AFRU7XL4AOF6LAVCNFSM6AAAAACNRKTOYGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTMMRRGUYDINBXGI> . You are receiving this because you were mentioned.Message ID: ***@***.***>