Re: Avoiding OOM on overcommit...?

From: Jesse Pollard (pollard@cats-chateau.net)
Date: Mon Mar 20 2000 - 21:50:08 EST


On Mon, 20 Mar 2000, Horst von Brand wrote:
>Jesse Pollard <pollard@tomcat.admin.navo.hpc.mil> said:
>
>[...]
>
>> Without overcommit:
>> You can support 100 simultaneous connections, with full saturation of
>> each server, with no failures.
>>
>> Result: happy customers, happy management, maybe even a raise.
>
>Management nagging about supporting more pages, worried by waste of several
>Gb of disk that has never, ever been touched. System is sluggish, needs
>constant tweaking of "resource allocation quotas" as applications crash,
>even there are resources available. Seriously consider firing inept
>sysadmin.

Disk space is cheap.

System is no more sluggish than currently, and is much more reliable.

First, "constant tweaking" means the system was/is undersized, and the
accounting records justify the additional business support for expansion.

Second, If it is determined that overcommitment is necessary, then it can
still be done - along with the documentation on what happens when the system
crashes.

I've never been fired for guaranteeing system uptime.

Obviously you don't work where uptime is counted in the thousands of dollars
per hour.

>> If you overcommit:
>> You might support 100 simultaneous connections, but not full saturation
>> of each server, without aborting some connections or crashing the
>> server/system.
>>
>> Result: some unhappy customers, not so happy management, difficulty
>> in identifying problems, and definitely no raise.
>
>Other customers are unhappy because of long download times, NS (or
>whatever) crashing, not getting to the site because of (local or remote)
>network congestion. The "catastrophe" isn't even a blip on the sysadmin's
>screen.

Yup - long download times since the system keeps crashing, forcing the
customer to a different site and or different company.

If network congestion is the problem here, it is also the problem without
overcommit. There is no correlation there.

The catastrophe is loss of business, loss of reputation, going out of
business because you can't keep the customers.
>
>> So you used 2G byte of swap - I know where you can by 18GB of swap for about
>> $300 US...

-------------------------------------------------------------------------
Jesse I Pollard, II
Email: pollard@cats-chateau.net

Any opinions expressed are solely my own.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/



This archive was generated by hypermail 2b29 : Thu Mar 23 2000 - 21:00:31 EST