Term for inefficiency inherent in hierarchical allocation

Solution 1:

Given Dan's request in the comments to provide some kind of justification to the term Route Exhaustion, I'll offer an anecdotal response.

Firstly, it's important to distinguish between hierarchies and routes. Hierarchies can be used for parent-child relationships without ever suffering the problem mentioned in the original question. It could be departments, relationships, or any number of things, and many of them will not suffer the issue outlined because they don't rely on routing.

Routing requires a set of rules that allows us to quickly locate an entity based on a set of hierarchical rules that allow us to quickly (and efficiently) locate something. They work because the rules are simple, and they are fast to process. This is when you type "google.com" in to your browser it knows where to go.

To keep things fast and efficient, routing hierarchies (such as DNS, IP addresses), need to have limits. Therefore, given any IP address range (Ipv4):

First
    Second
        Third
            Fourth

Obviously, given the explosion of the internet, and the range of numbers available (0-255), this was eventually going to be exhausted.

Now consider a hierarchy where I do not care about routing:

 United States Of America
     Arkansas
         Bentonville
             Walmart HQ
                  Finance
                       Commercial
                            Frank

"But wait!" You say, that's a route!

No, it's not.

FAO: Frank, Finance: Commercial
Walmart HQ
Bentonville, AR, 72712, USA

Humans can read that. But to do something efficiently, you need computers! (Actually, a computer could probably read that and figure it out, but I think that's beyond the scope of the question).

Let's call Walmart

1
    800
         925
             6278

This, is a route. 1 is the USA, 800 is a freephone number, and then we have 925 and 6278. Alas my knowledge of US telecommunications is unsure of whether they are separate nodes, but if they follow the rest of the area codes on the exchange, they're probably separate. Anyone can see now, that as great as this looks, you'll eventually run out of numbers to give out at a particular node.

To surmise, in the example of a departmental hierarchy, we rarely have to travel it, and we don't even have to travel it as address (though the zip-code may still play a part!), I don't have to route through many objects in my code.

But when you dial a number, and when you have an IP address, you have to route it.

When you run out, it's route exhaustion. You've exhausted all possible routes.

Wow, this answer really is a lot of waffle :)

Solution 2:

This is not a question of hierarchy. @Moo-Juice gives a good example that contrasts hierarchy with a route, showing that hierarchy is not the question. But neither is routing. Non-North American international telephone numbers have a much easier time routing:

• 00 + country code + city code + local number

When the city grows, the city code may be able to be shortened, and the local numbers can always be made longer, up to any needed number of digits. The number of available telephone numbers never runs out.

The trouble comes when the number of digits must be restricted.

Thus the issue is neither one of hierarchy nor routing, it is one of encoding: how do I get all the information needed into a fixed set of codes? In this case, a fixed number of digits in a certain format.

Thus, the question is answered by Information Theory, created by Claude Shannon. The issue you bring up is described as [Shannon entropy][1].

[1]: http://en.wikipedia.org/wiki/Entropy_(information_theory) "Shannon entropy".

Read especially the second paragraph, where it says, "the entropy (thought of as the average information) received from non-uniformly distributed data is less than log2(n)."

Solution 3:

The costs of hierarchy is an expression that may suggest the concept of the inefficiencies derived from hierarchical allocations.

The following study shows that hierarchical organisations are less inefficient that it is generally expected, but systematic weaknesses and distortions appear to be unavoidable.

• Some two-fifths of principals did not delegate even when income-maximization required it. This suggests that people get a non-pecuniary buzz from being in control, and seek this benefit at the cost of economic payoffs to themselves and others.

• This is consistent with the findings of other experiments by Fehr and colleagues, which suggests that hierarchy facilitates exploitation rather than pure economic efficiency.

Solution 4:

This issue of compounding inefficiencies seems to be an endemic feature of any hierarchical system because its nature is exponential by definition.

That said, several hours of research led to interesting results from various sources and systems that experience the multiplicative deleterious effects resultant from a multi-leveled system.

I think some of these disadvantages could be summarized with terms like tier-degraded (from the perspective that additional steps in the chain compound the problem) or vertically-challenged utilization (in more of a corporate tone relating to stratum-enhanced challenges of properly apportioning resources evenly). Additionally, depth-compounded decay may indicate the exponential worsening of a particular property in a system.

However, as has been presented earlier, the appropriateness of the term you select may vary with the reason for presenting hierarchy as a disadvantage -

• From the perspective of the inefficiency to manage or disburse resources on a 1:1 basis, concepts around organizational inequality and artificial scarcity start to take on meaning.
• Alternatively, if examined from the approach where the forcing of hierarchy results in the stratification (and subsequent limitation) of significant routes or signals required to satisfy all stakeholders in the system, things such as distinctive path deficiency or lack of discrete channels may suffice to demonstrate unique insufficiency, such as in the area code/IP4 case presented above.

Interestingly, it's worth noting that there are additional disadvantageous results from hierarchical systems, such as exponential communication difficulty (for highly structured hierarchies) and limitations to modeling complexity which may not be immediately obvious but are surely no less significant.

Certainly a fascinating topic; its real-world implications (and realizations) are most intriguing!