3 ms·
I would actually expect the simple dequeue-deserialize-update-something-in-redis use case to be the "worst case" comparison and that the more work the go worker
by sanderjd 13y ago
I would actually expect the simple dequeue-deserialize-update-something-in-redis use case to be the "worst case" comparison and that the more work the go worker does, the better the performance numbers would look.
It seems like using something designed from the start for cross-technology communication (like 0mq) may be a better idea, but I suppose there is already lots and lots of existing resque client code out there.
- benmanns 13y agoYes, this is exactly what I was thinking. You can replace one single Resque worker to see how the performance improves without changing the front-end queuing or having to run an additional queuing server
- steveklabnik 13y agoSince jobs are just encoded as JSON into Redis, it's pretty already cross-technology compatible. Furthermore, we're committing to a format specifically for Resque 2.0, so you can guarantee that you'll be interoperable.
- sanderjd 13y agoNeat. I really like the idea of Resque being able to be thought of as a protocol specification plus a reference client and server implementation.