p_manage_01: run time; work space used at University of Minnesota

Last updated
Save as PDF
Share
1. Share
2. Tweet
3. Share

Article Type: General
Product: Aleph
Product Version: 20,22

Description:
p_manage_01: run time; work space used at University of Minnesota (and U. Quebec).

Resolution:
From Janet Arth at U. Minnesota:

p_manage_01:
p_manage_01, 8 processes, in umn02 [parallel library]:
start: Tue Sep 13 12:32 2011
end: Thu Sep 15 09:56 2011

archive logging = yes
152 a-cycles
78 e-cycles

6085304 bib records (last-doc-number)
54995041 keywords (last-word-number)

Time to move the umn02 data to umn01:
Time to export from umn02 using p_file_03 (this was done in advance of the actual switch on Sunday)
z95 (17 G) 8:10 - 8:22 ~12 minutes
z97 (29.875 G) 8:22 - 9:10 ~50 minutes
z98 (3.25 G) 9:10 - 12:24 ~2 hours 15 minutes
Less than 4 hours

We had the Oracle DBA back up the umn01 z95, z97, z98, z980 on Sunday morning right before starting the import "just in case" (she used the Oracle data pump for this and that took less than an hour).

Time to import to umn01 on Sunday morning using p_file_04
z95 7:06 - 7:46 ~40 minutes
z97 7:46 - 8:15 ~30 minutes
z98 8:15 - 9:01 ~15 minutes
Less than 1.5 hours

Temporary space used during indexing:
TMPDIR: maxed at 2.8 additional (peaked at 9/15/2011 12:14 AM)
UMN02 scratch: maxed at 106G additional (peaked at 9/15/2011 7:45 AM)
UMN02 files: maxed at 6.7 G (peaked at 9/15/2011 8:46:11 AM)

Post indexing space
UMN02 scratch: at the end had 74G of residuals to clean-up (notably the manage_01_4.X files)
UMN02 files: export size of z95, z97, z98 (after p_file_03 was run): 41G

Another run (from U Quebec): 18 Jan 2020: With 3.6 million bib records, manage 12.5 hours, and used approx 30 gb in /exlibris.

There is also info on this in "How To Run Index Jobs": section 5.1 (work space); section 10 (time).

Article last edited: 10/8/2013