3 ms·
Patron, from here: https://github.com/toland/patron https://github.com/toland/patron. We use it in combination with our (open source) FastSend gem to keep the s
by WJW 9y ago
Patron, from here: https://github.com/toland/patron https://github.com/toland/patron. We use it in combination with our (open source) FastSend gem to keep the streamed data away from the Ruby garbage collector, since it gets a bit emotional if it has to clear out hundreds of MBs every second. If you're interested why we chose this architecture instead of just redirecting to S3, our lead engineer gave a talk about the reasoning behind this structure. You can find the slides at https://speakerdeck.com/julik/streaming-large-files-with-ruby https://speakerdeck.com/julik/streaming-large-files-with-rub....
- raggi 9y agoYou can fill GB/s with net/http. You could do so easily with 1.9. The GC shouldn't be a problem unless your object graph is very complicated.