|
![](/i/fill.gif) |
On 08/03/2011 05:09 PM, Darren New wrote:
> Invisible wrote:
>> Poor performance is the exact opposite of scalability.
>
> I think it depends on whether you're talking about scalable at runtime
> or scalable at coding time. I.e., is it a question of how big a program
> you can write, or a question of how big a program you can run?
I've not seen it applied to code size. Usually it's applied to run-time
performance. (E.g., if you have a program that uses an O(N^2) algorithm,
it probably works just fine for 10 users, but it's going to fail
spectacularly for 10,000,000 users. It does not "scale".)
--
http://blog.orphi.me.uk/
http://www.zazzle.com/MathematicalOrchid*
Post a reply to this message
|
![](/i/fill.gif) |