用户测量 Hyperliquid 订单修改延迟高达 880ms

Quick question for anyone running latency-sensitive execution on mainnet: what's a realistic round-trip to modify/replace a resting order — request sent to accepted-ack received? I'm measuring ~880ms+ per op, which lines up with the Glassnode numbers and looks like mostly engine processing, not network. Three things I'm trying to figure out: 1. Does a single modify (or batched cancel+place) come back faster than sequential cancel-then-place, or roughly the same? 2. Is ~880ms the real floor on current mainnet, or are people getting sub-500ms acks with priority fees / colocation / running a node? 3. Do maker strategies here actually run sub-second reprice loops, or is the norm to quote wider and reprice less because the round-trip makes tight repricing impractical?

Quick question for anyone running latency-sensitive execution on mainnet: what's a realistic round-trip to modify/replace a resting order — request sent to accepted-ack received? I'm measuring ~880ms+ per op, which lines up with the Glassnode numbers and looks like mostly engine processing, not network. Three things I'm trying to figure out: 1. Does a single modify (or batched cancel+place) come back faster than sequential cancel-then-place, or roughly the same? 2. Is ~880ms the real floor on current mainnet, or are people getting sub-500ms acks with priority fees / colocation / running a node? 3. Do maker strategies here actually run sub-second reprice loops, or is the norm to quote wider and reprice less because the round-trip makes tight repricing impractical?

now for my 2nd - whats the usual latency yall are experiencing in getting matched AFTER you hit the JP AWS endpoint? For me from EU i got around 200-250ms on a GET/POST to the endpoint and then around ±700-800ms more to get the order filled and matched. Is that correct or am i maeasuring it wrong?

now for my 2nd - whats the usual latency yall are experiencing in getting matched AFTER you hit the JP AWS endpoint? For me from EU i got around 200-250ms on a GET/POST to the endpoint and then around ±700-800ms more to get the order filled and matched. Is that correct or am i maeasuring it wrong?

or maybe to ask it in an even better way - for those api-traders that act as takers - how often do you actually get filled on the IOC orders you submit?

or maybe to ask it in an even better way - for those api-traders that act as takers - how often do you actually get filled on the IOC orders you submit?