Welcome Serena Central users! CLICK HERE
The migration of the Serena Central community is currently underway. Be sure to read THIS MESSAGE to get your new login set up to access your account.
Absent Member.. tbanera Absent Member..
Absent Member..

Re: Initial TRIM reindex from existing Document Store - Performance

This is all with HP TRIM 7.3.1.

 

Also wanted to say thanks to Ryan and the rest for helping us get here.

 

T

0 Likes
EWillsey Acclaimed Contributor.
Acclaimed Contributor.

Re: Initial TRIM reindex from existing Document Store - Performance

Absent Member.. tbanera Absent Member..
Absent Member..

Re: Initial TRIM reindex from existing Document Store - Performance

Sorry one more thing.  We are still try a few things but this is likely our final config.

 

The one we are playing with is this setting:  FlushLockFile=E:\HPTRIM\IDOL\FlushLockFile.lck 

 

Thanks.

 

Tim

Highlighted
Micro Focus Expert
Micro Focus Expert

Re: Initial TRIM reindex from existing Document Store - Performance

Tim, your team did some amazing work digging into the details.  I've been in spectator mode the last few weeks 😉

The newest document, KM00387430, is designed to make sure your default instance is functional based on using the logs & test index batches.  Useful steps. 

What Tim has posted is more detailed in that it shows the critical settings & values needed to successfully reindex a large dataset with optimum efficiency.  And, despite IDOL recommendations against a Virtual Server, it's all done with Virtual Servers.

 

As Tim pointed out, the key is memory allocation during the reindex, having instances on multiple physical drives/LUNs, using the flushlock if you have multiple Content Services that must share a drive/LUN.  Also, noting the correct placement of custom settings is key, as well as to which config file you're applying them.

JasonIMEX Outstanding Contributor.
Outstanding Contributor.

Re: Initial TRIM reindex from existing Document Store - Performance

Great Thread thanks guys..

 

One question though. Anyone having issues with the dih incoming and failed folders growing and not being flushed?

 

Seems they just sit there growing with no end in sight.

 

 

HP Records management suite specialists
www.imexwa.com.au
0 Likes
JasonIMEX Outstanding Contributor.
Outstanding Contributor.

Re: Initial TRIM reindex from existing Document Store - Performance

Bumping for great justice!!

HP Records management suite specialists
www.imexwa.com.au
0 Likes
Micro Focus Expert
Micro Focus Expert

Re: Initial TRIM reindex from existing Document Store - Performance


JasonIMEX wrote:

Great Thread thanks guys..

 

One question though. Anyone having issues with the dih incoming and failed folders growing and not being flushed?

 

Seems they just sit there growing with no end in sight.


I'd say there's something wrong. Check the logs. DIH incoming should clear as the data files are successfully transferred to the content engines for processing.


Neil

Note: Any posts I make on this forum are my own personal opinion, and unless stated otherwise do not constitute a formal commitment on behalf of Micro Focus.

(Please state the version of CM you're using in all posts.)

MySupport: https://softwaresupport.softwaregrp.com/
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.