×
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.
The length of the save duration didn't really change that much. Summary,
only chopped off 5 minutes by using three less of our 70GB disk drives.
What's the deal, it's the number of the files and not the size? So did we
save the 5 minutes by removing the 800+ insignificant l_ archive log
files and not by the compression of the large files which freed up over
200GB?
Before compression:
05/11/09 17:32:13 start
05/11/09 19:01:48 2017181 blocks processed for sequence 1, volume AMON15
05/11/09 20:33:31 2042477 blocks processed for sequence 1, volume AMON25
05/11/09 21:00:36 576892 blocks processed for sequence 1, volume AMON35
05/11/09 21:00:40 4308 objects saved.
After compression:
05/18/09 17:32:12 start
05/18/09 19:01:48 1742161 blocks processed for sequence 1, volume AMON11
05/18/09 20:33:45 1747936 blocks processed for sequence 1, volume AMON21
05/18/09 20:55:23 387384 blocks processed for sequence 1, volume AMON31
05/18/09 20:55:26 3555 objects were saved on volumes AMON11 AMON21 AMON31
And if I only have about 850+ files where are the rest of the 3555 objects
saved coming from? OBJ(('/ARCHIVE1/*'))
Note: Turns out a bulk of them are in /ARCHIVE1/NOTES/DATA/domino and are
somewhat static.
Sometime when the server is down I should probably
- delete the *.tmp files
- move the one archive file out of the DATA directory and into the
DATA/ARCHIVE directory. Just for cleanup reasons.
- remove the full text index over the archive of the fellow who's been
gone for 3 years. (ties up 238MB in the FT alone)
Rob Berendt
As an Amazon Associate we earn from qualifying purchases.
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.
midrange.com
