too many "too many concurrent REQs" #24
Labels
bug
Something isn't working
Comments
|
That message is from StrFry, which caps subs at 20 per connection. Extremely low if we want just one filter per sub. |
|
I know, that will have to change eventually. |
|
Better get this started.. It takes a long time for operators to update their strfry versions |
|
I've increased the limit for metadata batch requests to 200 (previous is 20), so this issue should be fixed now. I've also added loading of cached metadata and chat rooms on startup. All necessary data will be loaded during startup, and users will only need to wait the first time. Screen.Recording.2025-05-21.at.18.55.22.mov |
|
Very nice. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I'm getting way too many of these
Received NOTICE. url=wss://user.kindpag.es msg=ERROR: too many concurrent REQsfrom multiple relays. wss://user.kindpag.es and wss://relay.primal.net show up to me on the console now.I don't know what request is triggering this, but given that user.kindpag.es is involved I imagine it's for
kind:0profiles? Maybe you're not closing the subscriptions after getting the events? Maybe it would be better to group multiple profile requests in the same filter? Ultimately these groupings should be unnecessary, and I think relays will learn that and start relaxing their limits, but for now it might be good.Also given that I have a lot of chats the first time I loaded the app they took a while to load, but then after a restart they also took some non-negligible time, which tells me Coop is not caching these profiles locally, so maybe that's something that could help. I don't know.
The text was updated successfully, but these errors were encountered: