RE: Database I/O Modernization -- 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.

Regarding SQL vs RLA performance, that's a YMMV thing.

-----Original Message-----
From: D*B [mailto:dieter.bender@xxxxxxxxxxxx]
Sent: Friday, September 15, 2017 9:03 AM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Subject: Re: Database I/O Modernization

<Carel>
Well, repositioning file pointer, for instance, to get another record from the PF/table.
Dealing with a PF with 100.00 records are more have impact on performance, </Carel>

100.00 or 100.000 is not a lot. I've worked with tables having hundreds of millions records and we did it all with SQL, not a single programm with RLA and it performed by far better, than RLA would have done, we did use commit and all data access was transaction safe. Batch processes running on recent hardware it doesn't help wether your cpu usage is 5% or 3%, the problem is to use all available hardware and bring all processors to its full power - in other words: use 100% of CPU power. Talking about interactive work, it's not at all important, if the retrievel of maybe 100 records uses 20 milliseconds or 200 milliseconds.

D*B

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.