× 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.



You can also refer to an earlier discussion thread in 200 regarding the
same from the site





Raul A Jager <raul@abc.com.py>@midrange.com on 12/23/2002 06:10:27 PM

Please respond to rpg400-l@midrange.com

Sent by:  rpg400-l-admin@midrange.com


To:   rpg400-l@midrange.com
cc:

Subject:  Re: Retrieval of data from memory

Leave it up to the operating system.

For a long time I tried to optimize the use of the hardware.  In early
computers we could even force files that are procesed together to be
allocated in alternating tracks in the disk.

If you have a small file, the OS will keep the whole thing in memory
without you doing anything.  Puting the data in "memory" may cause the
pages to be swapped to disk.  I'm sure the memory management from the OS
can be improved, but most of our attempts will cause more trouble than
help.  Concentrate in the "bussiness part" and leave the memory
management to the OS.

Raul
__________________________________________________________________________________________

Saunders, Robin wrote:

>Hi all,
>
>I need to write a program that reads data into memory, as this data is
>accessed many 10,000's of times a day and so I am trying to avoiding
>constant access of the data on disk. There is no fixed limit on the number
>of records in the file, but probably would be a maximum of 100.
>
>I thought of using an array and lookup op. code on the key of the file.
Is
>there any better ways of achieving my desired result?
>
>Also, would managing the memory allocation for the array make a
significant
>difference to performance?
>
>TIA, and Happy and relaxing Holidays to all.
>
>Regards,
>Robin
>~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>Robin Saunders
>Principal Consultant
>Misys International Banking Systems, Inc.
>Tel: +63 (2) 885 0351 to 80 local 1202
>Fax: +63 (2) 885 0327
>Mobile: +63 (0) 917 530 6499
>Email: robin.saunders@misys.com
>~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>
>This email message is intended for the named recipient only. It may be
>privileged and/or confidential. If you are not the intended named
recipient
>of this email then you should not copy it or use it for any purpose, nor
>disclose its contents to any other person. You should contact Misys
>International Banking Systems as shown below so that we can take
appropriate
>action at no cost to yourself.
>Misys International Banking Systems Ltd,1 St George's Road, Wimbledon,
>London, SW19 4DR, England. Email: ibs.postmaster@misys.coms.com Tel: +44
(0)
>20 8879 1188 Fax: +44 (0) 20 8947 3373
>Misys International Banking Systems Ltd is registered in England and Wales
>under company no. 971479
>
>
>_______________________________________________
>This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list
>To post a message email: RPG400-L@midrange.com
>To subscribe, unsubscribe, or change list options,
>visit: http://lists.midrange.com/cgi-bin/listinfo/rpg400-l
>or email: RPG400-L-request@midrange.com
>Before posting, please take a moment to review the archives
>at http://archive.midrange.com/rpg400-l.
>
>

_______________________________________________
This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list
To post a message email: RPG400-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/rpg400-l
or email: RPG400-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.





As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.