If an application is allocated less budget than it requires, then this could result in under-provisioning, affecting its performance, and consequently quality of user experience.
On the other hand, if an application is allocated too much budget, then it can result in over-provisioning and consequently, resource-underutilization (see Fig. 1).
When the Internet data budget plan period starts, every application is allocated a certain amount of reserved budget based on their priorities assuming all the applications have equal bandwidth usage.
Initially, all applications are allocated one web server instance in each resource allocation interval.
Figure 4 b depicts that under-provisioning penalty decreases with larger amount of allocated budget as the applications are allocated adequate amount of budget.
Figure 4 c depicts that average penalty decreases with larger amount of allocated budget as the high-priority applications are allocated adequate amount of budget according to their bandwidth requirement.
Again, high-priority applications are stuck when the flexible budget is depleted, but in the case of H-IDM, high-priority applications are allocated flexible budget repeatedly according to their requirements.
Hong Kong's first fund, which was allocated by bureaucrats, routinely saw applications languish for nine months or more, a lifetime for a start-up.
The Netherlands was allocated 13.
($109 million of that was allocated to Google and $73 million was allocated to Motorola).
From Fig. 3, initially each application a is allocated one resource instance of the appropriate flavour at each tier n and for each resource allocation interval t.
