Grokking Concurrency in Python
Vote

0% completed

​

Leaks in Long-Running Workers

Suppose a worker keeps 4 KB that it never releases for every page it fetches, and it fetches 10 pages per second. That is about 144 MB per hour and 3.5 GB per day. A five second test sees only 200 KB of growth, while a worker with a 2 GB memory limit reaches that limit in about 14 hours. Each piece of work looks correct; the trouble is in what the work leaves behind.

What a Leak Is

**A leak in a long-running worker is anything that grows with the amount of work done and is never released, such as tasks, queue items, open connections or memory

.....

.....

.....

Like the course? Get enrolled and start learning!

Reading Progress

0%


Vote for new content