Replying to Avatar Mike Dilger ☑️

Since I released Chorus, there have been 5 point releases. Each one is because of a significant bug. There has been other work, only the significant bugs fixed are listed here:

Version 1.0.1: FIX: AUTH was broken (bad time comparison)

Version 1.0.2: FIX: Deletion of replaced replaceable events was deadlocking

Version 1.0.3: FIX: LIMIT was happening before screening, so the total events supplied was often too low.

Version 1.0.4: FIX: Events after EOSE were not being screened.

Version 1.0.5: FIX: A tokio runaway performance issue is resolved.

I'm pretty happy with how the relay is operating now. I've tested a number of things and behavior is as expected.

As for peformance (since the 1.0.5 fix), it is using 0.58 seconds of CPU time per hour.

Compare that to my nginx daemon is using 285 seconds of CPU time per hour.

Avatar
Mike Dilger ☑️ 1y ago

BTW I'm running my chorus relay on port 444 without any reverse proxying, doing all the SSL in rust. Banned IPs get dropped prior to SSL setup.

Reply to this note

Please Login to reply.

Discussion

No replies yet.