3 ms·
nuclio is using a real-time arch (no context switch, zero copy, no Ser/Des, parallelism, .. ) Go function serves 400K events/sec/proc, Py does 70K events/sec/pr
by yaronhaviv 9y ago
nuclio is using a real-time arch (no context switch, zero copy, no Ser/Des, parallelism, .. ) Go function serves 400K events/sec/proc, Py does 70K events/sec/proc, this is faster than running your own function with standard HTTP serving on a bare-metal server.
for comparison most serverless frameworks do 1-5k events/sec and up to 100x higher latency.
disclosure: i work on nuclio
- rburhum 9y agoMy point is that - as described - it is a dumb comparison. > open source serverless platform which is faster than bare-metal code does't make sense. It eventually has to run on top of bare metal (via hypervisor or directly), so claiming that something that eventually runs on top of bare metal is "faster than bare metal" doesn't make sense at all.