Performance of *MAX4GB files vs *MAX1TB -- 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.



I think I remember John Sears stating at a COMMON presentation that physical
files created with the parameter ACCPTHSIZ(*MAX1TB) will perform better than
'old' files created at *MAX4GB since they execute a different (newly written)
code path when they are accessed.

Has anyone had a chance to see if it's worthwhile changing old physical files to
*MAX1TB to realize a performance benefit?  (Perhaps someone with a standalone
machine for testing)?

Scott Lindstrom
Zenith Electronics


+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---

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.