Getting in / Pair 14 of 41
A wait somebody planned against a wait nobody did
Waiting is waiting, from where you sit. The difference is whether somebody decided you should wait or whether the request simply never came back.
Why waiting feels the same in both
Time passes and nothing arrives. That is the entire shared surface, and it is enough to make people treat the two as one thing. Both waits are open ended from your side, both are silent about how long they will last, and both come at the exact moment you wanted to get on with something.
The distinction is not really about how long you wait. It is about whether anybody on the other side knows you are waiting. In one case you are a number in a line that somebody built on purpose. In the other you are one of a great many requests piled against a door that is not opening fast enough.
A holding pattern put there on purpose
The operator has decided that letting everybody in at once would break things, so arrivals are held and admitted in order. A queue is a piece of the site like any other page. It was written, it was designed, and it will normally tell you that it is what it is.
No plan, just more demand than capacity
Requests are arriving faster than they can be served, so some of them time out, some come back half drawn and some return an error. Nothing is holding your place, nothing is counting, and there is no order to be next in.
Where the wait is being decided
A queue is a decision made in advance. Somebody sat down, worked out that the front door needed a valve, and built one. That means the queue has a purpose, a message and usually some idea of progress, since a valve that told you nothing would be worse than no valve at all.
Overload is what happens when nobody built the valve, or when the valve is behind the part that is struggling. It has no message, no order and no memory of you. Two requests sent a minute apart can behave completely differently, since each one is just taking its chances.
| What you are given | A queue | An overload |
|---|---|---|
| The page | Written for the purpose and says what it is | The ordinary page half drawn, an error, or nothing at all |
| Asking again | Puts you back in the same place, or further along | Behaves differently every time you try |
| What it tells you | That you are waiting and roughly what for | Nothing, or a generic failure |
| The rest of the site | Held behind the same wait, consistently | A mixture of parts that work and parts that do not |
The tell that separates a queue from a jam
Read the page, not the clock
Look at whether the thing in front of you is a page somebody wrote or the absence of a page. A queue names itself, since a holding pattern that kept quiet would defeat its own purpose. Overload cannot name itself, and produces a failure or a blank instead.
- Read what is actually on the screen rather than watching the tab spinner.
- Ask whether a person wrote that text for this exact situation, or whether it is the generic failure any site would show.
- Ask again a couple of minutes later and see whether the answer is the same shape twice.
Consistency is the second half of the tell. A queue is boringly reliable, since being reliable is its job. Overload is erratic, and erratic behaviour is the clearest thing you will get in the absence of a message. Two very different looking answers a minute apart mean nobody is managing your wait.
Getting this pair backwards
- If you read a queue as overload
- You abandon a working entrance mid wait and go looking for another address. That is the most expensive move on this page by a wide margin, since the searching is the risky part, not the waiting.
- If you read overload as a queue
- You sit and wait for a place in a line that does not exist. You lose the evening and possibly a window you wanted to act in, but you end the night at the same address you started at.
Waiting badly costs you time. Leaving badly costs you rather more, since the moment you start hunting for a way in is the moment your judgement is at its weakest. This site monitors nothing and reports no status for any address, and that is deliberate, since a page claiming to know what is reachable right now would be the same trap wearing a different hat. The general form of that argument is on how pairs work.
What each of the two wants you to do
- If it is a queue
- Leave the tab alone and let it do the counting. Reloading a queue commonly puts you at the back rather than the front, which is the opposite of what the reflex expects.
- If it is overload
- Stop asking for a few minutes. Repeat requests add to the pile you are stuck behind, and coming back later to the address you already had is the whole of the correct response.
A queue that has clearly stopped moving for a long stretch has quietly become the other half of this pair, and it deserves the same treatment as overload. The neighbouring refusals in getting in cover the ones that happen at the form rather than in front of it, and the separating tests for every pair are collected at tests.
Questions readers send about this pair
Does a long queue mean the market is about to fall over?
No, and it can mean the opposite. A queue exists so that the thing behind it does not fall over, which makes it a sign somebody planned for load rather than a sign that nobody did.
Will refreshing get me through faster?
Generally the reverse. A queue that tracks arrivals may treat a refresh as a new arrival, and under load a repeat request is one more thing for an already busy server to drop.
How long should I wait before giving up for the night?
There is no number worth printing here, and nothing on this site watches anything, so any figure would be invented. The useful rule is that giving up for the night is fine and going looking for a new address is not.