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


  • Subject: RE: LIBL limitation of 25 libraries
  • From: Joe Teff <jteff19@xxxxxxx>
  • Date: Fri, 27 Nov 1998 13:58:15 -0600

> I would think that the overhead is not linked to the number of entries in the 
>libl
> but to the number of object the system have to go trought. I think that there 
>is
> not a big difference when searching in one library with 1000 object or in 10
> libraries with 100 object.

I have not been in the role as "performance advisor / investigator" since back 
in
my days on the S/38. I would assume that the AS/400 behaves very similarly.
I remember attending sessions at COMMON where we were told that the
number of libraries in the library list is a factor for performance. We were
told that the higher up in the list an object was found, the better the 
performance.
If a majority of your objects were found within the first couple of libraries, 
you
wouldn't see any degradation. Because of this, I've always been more concerned
about the organization of the library list rather than the length.

Joe Teff

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