Fedify: an ActivityPub server framework
If you're on the fence about which driver to choose for #Fedify's message queue, here's a benchmark that just came out. In addition to no queue, we compare 5 drivers, for a total of 11 setups:
- No queue
InProcessMessageQueueDenoKvMessageQueueRedisMessageQueuePostgresMessageQueueAmqpMessageQueueInProcessMessageQueue× 4DenoKvMessageQueue× 4RedisMessageQueue× 4PostgresMessageQueue× 4AmqpMessageQueue× 4
Curious to see the results? Check out the GitHub repository!
洪 民憙 (Hong Minhee)
@[email protected] · Reply to 洪 民憙 (Hong Minhee)'s post
@thisismissem Here's the benchmark, and while it contains some questionable results, the overall conclusion is as following:
• Response times are much faster with queues than without.
• Overall throughput is better without queues.
• However, some queue setups can achieve throughput close to that of no queue.
This benchmark assumes communication within a single node, so the effect of queues may be greater in real-world networks.
