Re: Explaining single level store to non i people -- MIDRANGE-L

Subject: Re: Explaining single level store to non i people
From: Nathan Andelin <nandelin@xxxxxxxxx>
Date: Tue, 18 Aug 2009 09:13:57 -0700 (PDT)
List-archive: <http://archive.midrange.com/midrange-l>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

"Typically, a Linux system will share code and system libraries among
processes so that there's only one copy of the code in memory at one
time."

I suspect the devil is in the details. So I'd just refer to Frank Soltis' books for details.

But some anecdotal evidence - I worked for a company that was running bookeeping operations (many applications) for a fairly large hotel & restaurant with OS/400 and about 50 workstation & printer sessions on a server with just 96 MB of RAM.

-Nathan.

As an Amazon Associate we earn from qualifying purchases.

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.