|
-----Original Message----- From: Scott.Lindstrom@zenith.com <Scott.Lindstrom@zenith.com> To: midrange-l@midrange.com <midrange-l@midrange.com> Date: Monday, November 22, 1999 5:34 PM Subject: Performance of *MAX4GB files vs *MAX1TB > > >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)? Well... a standalone machine won't answer your question. The major change is seizes. Seizes on the 4GB indexes are performed at the root node, so the whole index is seized. On the new 1TB indexes, the seizes occur at the leaf node that is being updated. So, if you have a very active machine and experience a large number of seizes (say 400 people banging JDE software, for example) then changing to the new indexes can probably improve your seize performance. The only way to tell, as with so many other performance issues, is to try it on YOUR machine and see. In the worst case, no performance benefit will be seen, but hey, you don't have to go back to the smaller indexes unless backward compatibility is an issue. =========================================================== R. Bruce Hoffman, Jr. -- IBM Certified AS/400 Professional System Administrator -- IBM Certified AS/400 Professional Network Administrator "The sum of all human knowledge is a fixed constant. It's the population that keeps growing!" +--- | 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 +---
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.