Artwork

Content provided by Tomasz Nurkiewicz. All podcast content including episodes, graphics, and podcast descriptions are uploaded and provided directly by Tomasz Nurkiewicz or their podcast platform partner. If you believe someone is using your copyrighted work without your permission, you can follow the process outlined here https://ppacc.player.fm/legal.
Player FM - Podcast App
Go offline with the Player FM app!

#42: Flow control and backpressure: slowing down to remain stable

4:13
 
Share
 

Manage episode 293875704 series 2680464
Content provided by Tomasz Nurkiewicz. All podcast content including episodes, graphics, and podcast descriptions are uploaded and provided directly by Tomasz Nurkiewicz or their podcast platform partner. If you believe someone is using your copyrighted work without your permission, you can follow the process outlined here https://ppacc.player.fm/legal.

Imagine two independent systems communicating with each other. One producing data and the other consuming it. There must be some place where data is buffered. Just in case the producer generated some data but the consumer is currently busy. For example, incoming requests, messages, packets - must wait. Sooner or later, this buffer overflows and either starts dropping data or crashes altogether. Moreover, large buffers imply growing latency between production and consumption. The consumer is perceived less responsive because data waited for a long time in queue. Especially when nothing is prioritized, so first come, first served. Also known as FIFO, first in, first out.

Read more: https://256.nurkiewicz.com/42

Get the new episode straight to your mailbox: https://256.nurkiewicz.com/newsletter

  continue reading

98 episodes

Artwork
iconShare
 
Manage episode 293875704 series 2680464
Content provided by Tomasz Nurkiewicz. All podcast content including episodes, graphics, and podcast descriptions are uploaded and provided directly by Tomasz Nurkiewicz or their podcast platform partner. If you believe someone is using your copyrighted work without your permission, you can follow the process outlined here https://ppacc.player.fm/legal.

Imagine two independent systems communicating with each other. One producing data and the other consuming it. There must be some place where data is buffered. Just in case the producer generated some data but the consumer is currently busy. For example, incoming requests, messages, packets - must wait. Sooner or later, this buffer overflows and either starts dropping data or crashes altogether. Moreover, large buffers imply growing latency between production and consumption. The consumer is perceived less responsive because data waited for a long time in queue. Especially when nothing is prioritized, so first come, first served. Also known as FIFO, first in, first out.

Read more: https://256.nurkiewicz.com/42

Get the new episode straight to your mailbox: https://256.nurkiewicz.com/newsletter

  continue reading

98 episodes

All episodes

×
 
Loading …

Welcome to Player FM!

Player FM is scanning the web for high-quality podcasts for you to enjoy right now. It's the best podcast app and works on Android, iPhone, and the web. Signup to sync subscriptions across devices.

 

Quick Reference Guide

Copyright 2025 | Privacy Policy | Terms of Service | | Copyright
Listen to this show while you explore
Play