80 seems a bit steep to me. nostr:npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z any comment on how many subs Amethyst needs to perform correctly?
Between 10 to 12 subs, each with rotating 10 filters each. We have to mix several goals in one sub, which destroys the efficacy of EOSEs.
I wish more relays worked on their sub/filter limits to a more reasonable amount. 30-40 should be enough for most clients, even heavier ones like Amethyst.
The bigger the amount of subs, the better the handling via EOSEs get and thus the smaller the traffic and frequency of filter updates get.
30-40 subs, each sub with 30-40 filters, each filter with 30-40 event kinds (some relays block by the number of kinds in a single filter).
That should be enough for everyone.
If all goes well, I’ll consider bumping this high.
makes sense
Right, my understanding (from way back in February or so) was that allowing more subs just means clients won't have to open additional connections to get their 'vents. Don't be modest client devs, how many subs do you *really want 😎
It’s a balancing act between perf on both ends. I’ve merged the change so hopefully my Amethyst friends will see improved performance.
hum... was Amethyst reaching your limits? I thought I tested your relays. I can double-check. Maybe we added some stuff that broke it :(
I have seen no indications of problems, but it was mentioned because I’ve opened parts of my config for public comment.
I want my users to have the best I can provide. That’s kinda how I ended up asking you into the thread. I don’t mind raising the limits if it provides your users (and mine) a better experience.
