该用户的聊天记录定位。
<@707597210845446214> I think there is a problem of tick_sizes in the orderbook websocket messages, they seem to be wrong or outdated
<@707597210845446214> I think there is a problem of tick_sizes in the orderbook websocket messages, they seem to be wrong or outdated
P99 below 100ms
P99 below 100ms
For me it's become quite good over the last hour
For me it's become quite good over the last hour
i think the dog sharted the CLOB's code
i think the dog sharted the CLOB's code
same, c7i.flex-large is well enough for now haha, and free 🙂
same, c7i.flex-large is well enough for now haha, and free 🙂
log times UTC, Dublin
log times UTC, Dublin
In 3 minutes on sport markets : 2026-06-05 15:03:20.477 | INFO | [LATENCY - POST_ORDERS] 2631 calls | Avg: 108.9ms | Min: 37.0ms | Max: 1217.0ms | P10: 46.0ms | P50: 66.0ms | P90: 224.0ms | P95: 335.0ms | P99: 609.0ms 2026-06-05 15:03:20.478 | INFO | [LATENCY - CANCEL_ORDERS] 2608 calls | Avg: 56.2ms | Min: 30.0ms | Max: 413.0ms | P10: 36.0ms | P50: 46.0ms | P90: 82.0ms | P95: 108.0ms | P99: 209.0ms 2026-06-05 15:03:20.478 | INFO | [LATENCY - CANCEL_ORDER] 3140 calls | Avg: 53.0ms | Min: 30.0ms | Max: 421.0ms | P10: 35.0ms | P50: 43.0ms | P90: 79.0ms | P95: 102.0ms | P99: 182.0ms 2026-06-05 15:03:20.479 | INFO | [LATENCY - POST_ORDER] 2168 calls | Avg: 84.7ms | Min: 33.0ms | Max: 1024.0ms | P10: 39.0ms | P50: 53.0ms | P90: 169.0ms | P95: 274.0ms | P99: 440.0ms post_orders see very high latency compared to cancels, this is only GTC post_only orders
In 3 minutes on sport markets : 2026-06-05 15:03:20.477 | INFO | [LATENCY - POST_ORDERS] 2631 calls | Avg: 108.9ms | Min: 37.0ms | Max: 1217.0ms | P10: 46.0ms | P50: 66.0ms | P90: 224.0ms | P95: 335.0ms | P99: 609.0ms 2026-06-05 15:03:20.478 | INFO | [LATENCY - CANCEL_ORDERS] 2608 calls | Avg: 56.2ms | Min: 30.0ms | Max: 413.0ms | P10: 36.0ms | P50: 46.0ms | P90: 82.0ms | P95: 108.0ms | P99: 209.0ms 2026-06-05 15:03:20.478 | INFO | [LATENCY - CANCEL_ORDER] 3140 calls | Avg: 53.0ms | Min: 30.0ms | Max: 421.0ms | P10: 35.0ms | P50: 43.0ms | P90: 79.0ms | P95: 102.0ms | P99: 182.0ms 2026-06-05 15:03:20.479 | INFO | [LATENCY - POST_ORDER] 2168 calls | Avg: 84.7ms | Min: 33.0ms | Max: 1024.0ms | P10: 39.0ms | P50: 53.0ms | P90: 169.0ms | P95: 274.0ms | P99: 440.0ms post_orders see very high latency compared to cancels, this is only GTC post_only orders
Up <@707597210845446214>
Up <@707597210845446214>
<@707597210845446214> <@1361217824776786031> <@1402074242211643422> Why do you increase rate limits when obviously the CLOB has trouble handling that many requests??? After restart it works quite fine but once all bots are started it goes downhill like crazy, so there is obviously trouble handling requests
<@707597210845446214> <@1361217824776786031> <@1402074242211643422> Why do you increase rate limits when obviously the CLOB has trouble handling that many requests??? After restart it works quite fine but once all bots are started it goes downhill like crazy, so there is obviously trouble handling requests
it's legal in some countries
it's legal in some countries
managed to open it with Dutch residency
managed to open it with Dutch residency
<@707597210845446214> Could you be more transparent on the problems you're facing and communicate more? It's been 10 consecutive maintenances with no significant upgrades now...
<@707597210845446214> Could you be more transparent on the problems you're facing and communicate more? It's been 10 consecutive maintenances with no significant upgrades now...
latency is already trash again
latency is already trash again
Please trade on my markets <:bidenok:1000341479086116884>
Please trade on my markets <:bidenok:1000341479086116884>
order post still lagging
order post still lagging
2026-06-05 13:11:42.405 | INFO | [LATENCY - POST_ORDERS] 3557 calls | Avg: 68.7ms | Min: 30.0ms | Max: 782.0ms | P10: 41.0ms | P50: 54.0ms | P90: 115.0ms | P95: 155.0ms | P99: 263.0ms 2026-06-05 13:11:42.406 | INFO | [LATENCY - CANCEL_ORDERS] 3526 calls | Avg: 44.0ms | Min: 25.0ms | Max: 538.0ms | P10: 31.0ms | P50: 39.0ms | P90: 59.0ms | P95: 71.0ms | P99: 117.0ms 2026-06-05 13:11:42.406 | INFO | [LATENCY - CANCEL_ORDER] 2776 calls | Avg: 43.4ms | Min: 25.0ms | Max: 374.0ms | P10: 31.0ms | P50: 38.0ms | P90: 59.0ms | P95: 69.0ms | P99: 106.0ms 2026-06-05 13:11:42.406 | INFO | [LATENCY - POST_ORDER] 1977 calls | Avg: 57.3ms | Min: 28.0ms | Max: 1024.0ms | P10: 35.0ms | P50: 44.0ms | P90: 86.0ms | P95: 123.0ms | P99: 253.0ms Bigger sample
2026-06-05 13:11:42.405 | INFO | [LATENCY - POST_ORDERS] 3557 calls | Avg: 68.7ms | Min: 30.0ms | Max: 782.0ms | P10: 41.0ms | P50: 54.0ms | P90: 115.0ms | P95: 155.0ms | P99: 263.0ms 2026-06-05 13:11:42.406 | INFO | [LATENCY - CANCEL_ORDERS] 3526 calls | Avg: 44.0ms | Min: 25.0ms | Max: 538.0ms | P10: 31.0ms | P50: 39.0ms | P90: 59.0ms | P95: 71.0ms | P99: 117.0ms 2026-06-05 13:11:42.406 | INFO | [LATENCY - CANCEL_ORDER] 2776 calls | Avg: 43.4ms | Min: 25.0ms | Max: 374.0ms | P10: 31.0ms | P50: 38.0ms | P90: 59.0ms | P95: 69.0ms | P99: 106.0ms 2026-06-05 13:11:42.406 | INFO | [LATENCY - POST_ORDER] 1977 calls | Avg: 57.3ms | Min: 28.0ms | Max: 1024.0ms | P10: 35.0ms | P50: 44.0ms | P90: 86.0ms | P95: 123.0ms | P99: 253.0ms Bigger sample
CLOB memory leaks for sure
CLOB memory leaks for sure
did not start full force
did not start full force
dublin
dublin
2026-06-05 13:04:21.838 | INFO | [LATENCY - POST_ORDERS] 16 calls | Avg: 41.1ms | Min: 32.0ms | Max: 63.0ms | P10: 33.0ms | P50: 36.0ms | P90: 62.0ms | P95: 63.0ms | P99: 63.0ms 2026-06-05 13:04:21.838 | INFO | [LATENCY - CANCEL_ORDERS] 17 calls | Avg: 32.9ms | Min: 26.0ms | Max: 50.0ms | P10: 26.0ms | P50: 31.0ms | P90: 40.0ms | P95: 50.0ms | P99: 50.0ms 2026-06-05 13:04:21.839 | INFO | [LATENCY - CANCEL_ORDER] 244 calls | Avg: 35.8ms | Min: 25.0ms | Max: 149.0ms | P10: 27.0ms | P50: 30.0ms | P90: 50.0ms | P95: 61.0ms | P99: 101.0ms 2026-06-05 13:04:21.839 | INFO | [LATENCY - POST_ORDER] 245 calls | Avg: 45.0ms | Min: 27.0ms | Max: 356.0ms | P10: 29.0ms | P50: 34.0ms | P90: 59.0ms | P95: 97.0ms | P99: 267.0ms
2026-06-05 13:04:21.838 | INFO | [LATENCY - POST_ORDERS] 16 calls | Avg: 41.1ms | Min: 32.0ms | Max: 63.0ms | P10: 33.0ms | P50: 36.0ms | P90: 62.0ms | P95: 63.0ms | P99: 63.0ms 2026-06-05 13:04:21.838 | INFO | [LATENCY - CANCEL_ORDERS] 17 calls | Avg: 32.9ms | Min: 26.0ms | Max: 50.0ms | P10: 26.0ms | P50: 31.0ms | P90: 40.0ms | P95: 50.0ms | P99: 50.0ms 2026-06-05 13:04:21.839 | INFO | [LATENCY - CANCEL_ORDER] 244 calls | Avg: 35.8ms | Min: 25.0ms | Max: 149.0ms | P10: 27.0ms | P50: 30.0ms | P90: 50.0ms | P95: 61.0ms | P99: 101.0ms 2026-06-05 13:04:21.839 | INFO | [LATENCY - POST_ORDER] 245 calls | Avg: 45.0ms | Min: 27.0ms | Max: 356.0ms | P10: 29.0ms | P50: 34.0ms | P90: 59.0ms | P95: 97.0ms | P99: 267.0ms
Like it ever happened <:Bidensmile:1040247925420339251>
Like it ever happened <:Bidensmile:1040247925420339251>
T'as pas dit chapeau
T'as pas dit chapeau
Chapeau toi d'abord
Chapeau toi d'abord
5 min latency? nice improvement <:Bidensmile:1040247925420339251>
5 min latency? nice improvement <:Bidensmile:1040247925420339251>
like up up
like up up
how up
how up
latency how info go fast
latency how info go fast
o7
o7
who's committing seppuku by starting their bot?
who's committing seppuku by starting their bot?
10% before taxes?
10% before taxes?
u just need to add a header {"user_id": "Mustafa"} and you have no delay
u just need to add a header {"user_id": "Mustafa"} and you have no delay
read the announcements, it says 12:10 UTC for 45 min
read the announcements, it says 12:10 UTC for 45 min
wasted on spawn
wasted on spawn
Both of you are right, it's just with their update, you can send more, but it's less useful to send more since you can't cancel during the delay
Both of you are right, it's just with their update, you can send more, but it's less useful to send more since you can't cancel during the delay
crazy that they can't fix this
crazy that they can't fix this
does not look like it, been this way for a month now
does not look like it, been this way for a month now
idk about taker rebates
idk about taker rebates
today's update introduces bugs
today's update introduces bugs
Like it does not work with 48000 let's increase to 120000 🤔
Like it does not work with 48000 let's increase to 120000 🤔
I dont understand how they prioritize increasing rate limits over having something that works with the current rate limits, every decision does not make sense
I dont understand how they prioritize increasing rate limits over having something that works with the current rate limits, every decision does not make sense
There are very expensive price feeds that allow you to be faster
There are very expensive price feeds that allow you to be faster
Else spreads would be very wide and you would be losing a lot of money
Else spreads would be very wide and you would be losing a lot of money
To prevent latency arb
To prevent latency arb
I dont think the first check is necessary
I dont think the first check is necessary
Skill issued on ragebaiting
Skill issued on ragebaiting
I think you're new 😂
I think you're new 😂
What about 5s maker latency on sports?
What about 5s maker latency on sports?
Another friday release, brace for impact
Another friday release, brace for impact
CLOB is on Mars
CLOB is on Mars
The team rn
The team rn
Polymarket