Doug Hoyte
Doug Hoyte
This is on my TODO list, I'm hoping to do it for next release. Thanks for making the ticket so I can track this. Counting is not a problem --...
Yeah, I saw that. Now I don't know what to do :) Negentropy is actually somewhat useful for this: You can sync the set of IDs across many relays, without...
Hi! I think most likely the reason for this is disk I/O. It's probably not exponential, but after it exceeds what can be held in the filesystem cache it causes...
Thanks for the info. FWIW I made a simple benchmark to see if the Negentropy object creation is scaling non-linearly. It appears to be linear, so I think it's likely...
Thanks for these! Something definitely seems off here -- I'm investigating.
Hi! Yes, I made some optimisations. They will be most effective if the DB is compacted. I didn't want to ask you to try it because there are still a...
Yeah, that looks like what I would expect. I just pushed a commit that adds a new config parameter: `dbParams.noReadAhead`. Can you please recompile and set that to true and...
I think you're right in that bitcoin nodes and nostr relays aren't directly comparable. In nostr you've got clients constantly making fairly relatively random queries that can retrieve data from...
Thanks for this! I'm looking into it. My first impression is that negentropy would be a more optimal solution.
I think this is a pretty good idea. Did you try starting a discussion on this in the NIPs repo? I'm a bit hesitant to add non-standard protocol extensions unless...