On Wed, Mar 10, 2010 at 12:06 PM, Lear Cale wrote:
> Which is what we mean by "cost". Price is what you are asked to pay.
> Cost is what you actually pay.
When discussing performance, "cost" would refer to what actually
impacts performance, as in "an expensive calculation".
Here the script memo
Which is what we mean by "cost". Price is what you are asked to pay.
Cost is what you actually pay. Thus the phrase "cost/benefit
analysis" -- not "price/benefit analysis".
On Wed, Mar 10, 2010 at 11:46 AM, Maggie Leber (sl: Maggie Darwin)
wrote:
> On Wed, Mar 10, 2010 at 11:43 AM, Lear Cale w
On Wed, Mar 10, 2010 at 11:43 AM, Lear Cale wrote:
> When we say how much memory a script is "actually using", that means
> the amount of memory the script is making semantic usage of. However,
> the script is *allocated* a larger amount. This larger amount is the
> amount that matters to the s
There's a semantic issue here that we need to clear up.
When we say how much memory a script is "actually using", that means
the amount of memory the script is making semantic usage of. However,
the script is *allocated* a larger amount. This larger amount is the
amount that matters to the syste
> It might be possible to add display of memory currently used
> as well, but what's the use case for it?
It would allow residents to independently review the imposed script limits.
Another use case would be because people *are* going to start banning
residents based on what the script limits UI
