×
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.
On 11 Sep 2013 07:24, Needles,Stephen J wrote:
<<SNIP>> We have a pretty good amount of memory and disk and are
not too concerned at this point about PAGESIZE, but will have to be
as we continue our trek. Is there a source to quantify the PAGESIZE
differences for planning purposes?
I am not aware of any specific docs, and my access to the InfoCenter
is problematic [so far] today. But basically, a simple arithmetic
representation can assist to help understand the effects. Given a key
size of 8-bytes, an 8K page size will have effectively 1K of key values
paged and accessible, but a 64K page size will have effectively 64K key
values paged. As /random access/ the key values being accessed from or
written to two different pages, results in 16K of paged memory in the
first example, but 128K of paged memory in the second. Of course 8X
memory requirements is maximal or worst-case with those two examples
[although I believe an 8-byte key is a 4K PagSiz], but given the nature
of keyed access and maintenance, the much larger page sizes as compared
to what would be typical\defaulted with DDS for RLA, could legitimately
significantly increase memory requirements.
http://archive.midrange.com/midrange-l/201211/msg00131.html
"... IIRC a "short" key actually uses a 4K page size, and smaller page
sizes can be better for non-query [RLA] activity and effects on journal;
i.e. for effective memory footprint."
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.
midrange.com
