Nostr

nostr:nprofile1qythwumn8ghj7mtvv44h2tnwdaehgu339e3k7mf0qyghwumn8ghj7mn0wd68ytnzv9hxgtcqypxgqqjh5ky2s2zf6pyczlptm2kesje953ddnak66ehy05a50caj75ukn0y if helpful, I can add a note in the benchmark docs clarifying this.

ᴛʜᴇ ᴅᴇᴀᴛʜ ᴏꜰ ᴍʟᴇᴋᴜ 5mo ago

what i was more so interested in was a tool that you run the relay and it hurls events at it and then queries it and times the full operation. such a tester could be pointed at any relay implementation then. certainly then you could add a script that builds and installs khatru and relayer, and probably since the secp256k1 library install script in scripts puts all the C/C++ things in, probably can also do strfry and the rust relay as well, by adding a rustup installer

i might do it myself at some point but feel free to do it if you like. it shouldn't be hard to add this to it.

seeing a side by side comparison of all of the relays would be great for seeing how good performance is but also how good each different relay is in comparison with each other on the same test workloads.

Reply to this note

Please Login to reply.

Discussion

Kyle 🐆 5mo ago

That's interesting... I'll work on this.

Kyle 🐆 5mo ago

nostr:nprofile1qythwumn8ghj7mtvv44h2tnwdaehgu339e3k7mf0qyghwumn8ghj7mn0wd68ytnzv9hxgtcqypxgqqjh5ky2s2zf6pyczlptm2kesje953ddnak66ehy05a50caj75ukn0y I put up an initial PR for this, let me know what you think. https://github.com/mleku/orly/pull/8

ᴛʜᴇ ᴅᴇᴀᴛʜ ᴏꜰ ᴍʟᴇᴋᴜ 5mo ago

i couldn't get it to all run, anyway, as we discussed, when it's all wrapped in a docker it will work for everyone.

now i've removed all those pesty serialization calls in the logging into closure logs, when logging is at default, it will go as fast as it can go.

i'm really curious to see how that works. i'm also curious how it comes to be that relayer is so freakin slow. and lol strfry. really. my goodness it's awful, and it's one of the most commonly deployed relays? wow.

probably lucky we haven't had the massive influx that some keep on complaining about.