docs: specify that the RPC endpoint is HTTP/S about convex-shutdown-simulation HOT 5 CLOSED

If we just change the below bullet to this, do you think that would be sufficient?

- - "Remote RPC" benchmarks used Alchemy as the RPC provider.
+ - "Remote RPC" benchmarks used Alchemy as the RPC provider, connected over HTTPS.

I am curious to see how performance compares between websockets and HTTPS. I'm not sure offhand if ganache and hardhat support it, but if so maybe we can add a second benchmark comparing those three over websockets?

from convex-shutdown-simulation.

Yeah, that's fine.

And yeah, I agree - if they support it, we should benchmark and compare. Otherwise, it's probably not a fair comparison 😄

from convex-shutdown-simulation.

Forgot to address IPC: I don't think I've ever come across any real usage/support of IPC either from dev framework or node operators like Infura and Alchemy. (I've also never really looked for it, so I could be wrong). But given that, it doesn't seem worth considering here

from convex-shutdown-simulation.

Just pushed 2b13971 which updates the docs, created #18 to track websocket benchmarks investigation/support!

from convex-shutdown-simulation.

Yeah, I don't think IPC is usable out of local fs. So node operators likely won't have any such support.

from convex-shutdown-simulation.