REUSEDLT and performance -- 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.

Are there performance implications when using REUSEDLT, especially on really 
large files? I have to think that there is at least some performance hit when 
REUSEDLT is enabled for files with millions of records. I'd guess that the 
system keeps some sort of index of deleted records, and serves one of those up 
when a WRITE is issued. I suppose, done correctly, the performance implications 
aren't too great; it would only affect deletes (add an entry to the index) and 
writes (fetch the record number from the index rather than just use the next 
sequential record).

Has anybody looked at this in any detail?
+---
| 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.