Skip to contentSkip to conversation

pull vs push (was Re: [bk patch] Make cardbus compile in -pre4)

DISCUSSION Jesse Pollard 1 participant 1 message Feb 11, 2002

lore
Share & tools
lore
#0 lore raw

--------- Received message begins Here ---------

Quoted 13 lines

Hi!

Quoted 10 lines
Quoted 3 lines

I don't see why everyone who is using BK is expecting Linus to do a pull. In the non-BK case, wasn't it always a "push" model, and Linus would not "pull" from URLs and such?

I'm all for it. I think it's a good thing.

In the absence of significant latency issues, pull scales better than push. It always has. Push is better in low bandwidth situations with lots of idle capacity, but it breaks down when the system approaches saturation.

Quoted 8 lines
Quoted 6 lines

Pull data is naturally supplied when you're ready for it (assuming no significant latency to access it). Push either scrolls by unread or piles up in your inbox and gets buried until it goes stale. Web pages work on a pull model, "push" was an internet fad a few years ago that failed for a reason. When push models hit saturation it breaks down and you wind up with the old "I love lucy" episode with the chocolate factory. Back in the days where

What's "i love lucy" episode?

It is an old TV show showing a queue overflow - The chocolate machine was producing candy faster than the personnell could handle and dispose of it.

I think it was being boxed - the skit starts out with the machine on slow, and a brief training session by a supervisor. The supervisor verifies that the candy was handled properly at the slow speed. Then she leaves. The machine makes a sudden jump in production, close to the limit of the personnel (Lucy and Vivian) who just manage to keep up.

Then the machine gradually increases the production rate. At first, they toss exess in to another box, then start trying to eat it, then dropping on the floor .... until the supervisor returns to turn off the maching.

-------------------------------------------------------------------------
Jesse I Pollard, II
Email: [email protected]

Any opinions expressed are solely my own.