In search of the fastest relay

https://pages.npub.info/test/relay/

https://image.nostr.build/a0e9a8686eca33b33f84a7c756fa500970af6efc867713a7bc466e87e0443997.jpg


For you it's fast. Others won't have it.


This is true.  That's because nostr doesnt have content delivery (yet).  400ms is considered unacceptably slow in most circles.  And most relays dont pass that test.


Im guessing it pings from your ip? Good way to check which vpns are fastest to which relays too! Also is ICMP over TOR a thing? Would love to know which onion relays are available and the uptime etc.


*most responsive from my network location

there i fixed it for you


There’s lag. But then there’s throughput.


lag is location, throughput is based on the capacity and replication of the deployment


My ping is ridiculous 🙄 https://image.nostr.build/a6198edeeaf0bddfd35556a4165985492e293aa60207784ecc86159dfabca833.jpg


Here's my results:
https://m.primal.net/LLxa.png


It is true.  Because we dont (yet) have CDNs.


a relay 'ping' is not like a web ping or an icmp ping. it has to upgrade to a websocket. so thats minimum 2x round trips, and then depending if you send or receive something in your check thats more round trips.


I mean it's not so important what the ping is, what matters is that the relays match for the users.


Great insight!  In fact many of the relays that I pinged didnt work at all.


Agree, but there's no way to do that right now.


yeah, it's a useless metric because it is noisy

what would be useful would be an average ping over a minimum 24 hour period

i could write a simple thing that would log the ping delays and make a EWMA graph that shows you its performance over time

the thing is that it's not just one thing... how much bandwidth this thing has, how many threads, which relay it's running, how many clients it gets, at what time, really a 24 hour sample is minimal to really evaluate... and measuring that against the bandwidth delivery as well, like, when you make big requests randomly across that 24 hour period, to count the time from request until the complete delivery... and probably you also want to in parallel have another evaluation of the quality of your connection to act as a baseline zero


well, the clients are all displaying these round trips now.. but they color stuff wrong, 400+ is red. whereas i consider 400ms round trip to be responsive from time connection initiated, to receiving a small req result.  400ms/4 == 100.  a typical 'ping' from west coast us to east coast.


Productivity soars when a computer and its users interact at a pace (<400ms) that ensures that neither has to wait on the other.

https://lawsofux.com/doherty-threshold/


id be curious to see everyones round trip timez (or their endorsed monitors) using nip66.

github.com/relaytools/monitorlizard


yes, and clients can account for this by showing really cool graphics about the connection status 😎


IMO if it's under 200ms it's laggy, but i'm an FPS gamer :)


In search of the fastest relay

https://pages.npub.info/test/relay/

https://image.nostr.build/a0e9a8686eca33b33f84a7c756fa500970af6efc867713a7bc466e87e0443997.jpg