The article called out 500usec as an upper bound for compute. How do you handle ... | Hacker News

Hacker Newsnew | past | comments | ask | show | jobs | submit

		carllerche on Dec 12, 2020 \| parent \| context \| favorite \| on: Thread-Per-Core Buffer Management for a modern sto... The article called out 500usec as an upper bound for compute. How do you handle heavier compute operations (TlS, encoding / decoding, ...)

agallego on Dec 12, 2020 [–]

on seastar, you yield a lot. so loops go from

    for( ... : collection) {}

to

   return seastar::do_for_each(collection, callback);

Consider applying for YC's Fall 2025 batch! Applications are open till Aug 4
Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact