So we compute in ~1ms, but we are running this out of ATL DC. I'm guessing Kalshi is somewhere else like US-EAST1?
So we compute in ~1ms, but we are running this out of ATL DC. I'm guessing Kalshi is somewhere else like US-EAST1?
该用户的聊天记录定位。
So we compute in ~1ms, but we are running this out of ATL DC. I'm guessing Kalshi is somewhere else like US-EAST1?
So we compute in ~1ms, but we are running this out of ATL DC. I'm guessing Kalshi is somewhere else like US-EAST1?
I'll take another look at my hot path something seems off thank you for the 1-2% validation
I'll take another look at my hot path something seems off thank you for the 1-2% validation
4/25 right now
4/25 right now
It's around ~70%
It's around ~70%
Hey, who can I speak to about RFQs? I keep seeing `{"error":{"code":"rfq_closed","message":"rfq closed","service":"midland"}}` even though we answer within `103ms (2ms priced + 98ms post)` I assume there has to be something more going on here?
Hey, who can I speak to about RFQs? I keep seeing `{"error":{"code":"rfq_closed","message":"rfq closed","service":"midland"}}` even though we answer within `103ms (2ms priced + 98ms post)` I assume there has to be something more going on here?