Aleksandr Razumov

> could we add IDs for each default exclude pattern? Looks good to me.

Sorry, no news. I'll try to debug it yet another time, but not sure that will succeed.

I'm trying to find a way to reproduce this issue. Tried something like that: ``` sudo ss -K dst 149.154.167.50 ``` Just closing connection does not reproduce this issue, so...

I've tried to reproduce it in #1293 using kubernetes + cilium network policy rules, but no success either.

``` Error: group: github.com/gotd/td/internal/mtproto.(*Conn).Run github.com/gotd/[email protected]/internal/mtproto/conn.go:214 - task readLoop: github.com/gotd/td/internal/tdsync.(*LogGroup).Go.func1 github.com/gotd/[email protected]/internal/tdsync/log_group.go:48 - read: github.com/gotd/td/internal/mtproto.(*Conn).readLoop github.com/gotd/[email protected]/internal/mtproto/read.go:193 - read: github.com/gotd/td/transport.(*connection).Recv github.com/gotd/[email protected]/transport/connection.go:70 - read intermediate: github.com/gotd/td/internal/proto/codec.Intermediate.Read github.com/gotd/[email protected]/internal/proto/codec/intermediate.go:73 - read length: github.com/gotd/td/internal/proto/codec.readLen github.com/gotd/[email protected]/internal/proto/codec/codec.go:35 - EOF...

Hey, I’m aware of this issue, but it is not trivial to fix. This issue is my top priority, that’s why it is still pinned. To make this issue fixed...

@jkaflik can you please share your benchmark so I can investigate this issue too?

I’m not working on this. Will try to take a look, but no ETA.

Thank you for your repsonse! I think that it is possible to measure low query latency, space efficiency and down-sampling. System performance under high multi-tenant load should demonstrate statshouse overall...

Agree with @erezrokah, adding this to docs (and probably providing a reference workaround + link this issue) would be very helpful. Also agree with @dmitry-shibanov that this feature should not...