RE: Why separate pools? -- MIDRANGE-L

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

Subject: RE: Why separate pools?
From: Alexei Pytel <pytel@xxxxxxxxxx>
Date: Tue, 23 Nov 2004 13:34:03 -0600
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>

<SNIP>
This does NOT work across memory pools.  If you have two users in two
different pools running order entry, you have two copies of the program
AND the data.  So running like jobs together in the same pool is really
good advice.</SNIP>

With all respect... This DOES work across memory pools.
As soon as page of a vurtual memory is addressable by machine, it does not 
matter, which pool it is in.
One practical use of this is SETOBJACC. One sets up a separate pool and 
preloads an object into that pool.
All users of the machine will benefit from it - regardless of the pool 
they run in.

    Alexei Pytel
always speaking for myself

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

RE: Why separate pools? , Joe Pluta
RE: Why separate pools? , Sue Baker

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.