New Member.

Performance guide?

Can anyone point to a good resource for optimizing Retain's performance? We believe we have optimal disk I/O performance, and we suspect our 10 messages/second processing speed is due to either our worker configuration (how many threads do these use?) or POA processing threads (does Retain use SOAP? Our POAs have the default 10 SOAP threads). Does QuickFinder indexing on the GW side come into play for the worker to find messages to archive? I've worked through the Retain installation guide and believe we have sufficient resources allocated to the Server+Worker and 2nd Worker VM.
3 Replies
AutomaticReply Absent Member.
Absent Member.

Re: Performance guide?


It appears that in the past few days you have not received a response to your
posting. That concerns us, and has triggered this automated reply.

These forums are peer-to-peer, best effort, volunteer run and that if your issue
is urgent or not getting a response, you might try one of the following options:

- Visit https://www.microfocus.com/support-and-services and search the knowledgebase and/or check
all the other self support options and support programs available.
- Open a service request: https://www.microfocus.com/support
- You could also try posting your message again. Make sure it is posted in the
correct newsgroup. (http://forums.microfocus.com)
- You might consider hiring a local partner to assist you.

Be sure to read the forum FAQ about what to expect in the way of responses:

Sometimes this automatic posting will alert someone that can respond.

If this is a reply to a duplicate posting or otherwise posted in error, please
ignore and accept our apologies and rest assured we will issue a stern reprimand
to our posting bot.

Good luck!

Your Micro Focus Forums Team

Knowledge Partner
Knowledge Partner

Re: Performance guide?

In article <TimHL.8e72cn@no-mx.forums.microfocus.com>, TimHL wrote:
> Can anyone point to a good resource for optimizing Retain's performance?

I was hoping someone could point us to one as well, but looks like we have
to try to figure this out from the basics.
I haven't even worried about performance as the biggest of our jobs only
takes about a half hour for about 4000 messages that hasn't been a problem
for us. Looks like we are getting about 2 messages per second where the
average message is larger than normal (CAD drawings and such to/from
Looking at the POA logs, Retain is clearly using SOAP, as well as looking
at the Worker config within the main Retain admin screens.
As I haven't seen Retain stuck on users' with stuck QuickIndexer, I don't
think they are related.

Versions can matter, so which Retain, GroupWise, and their hosts version
are we talking about? A number of updates to GW 2012 and 2014 where
specifically to improve SOAP performance.

POA status, are there errors as the worker threads do their thing? Are
GWChecks trying to run at the same time or anything else at the same time
touching the same resources (backup?).

How are the hosts' resources on both ends being used as the workers do
their thing?
How much CPU is being used and for what? Are they busy showing as
waiting? Time to watch top.
How much RAM is being used and are we hitting swap much?
How much resource contention at the hypervisor level?

Andy of
http://KonecnyConsulting.ca in Toronto
Knowledge Partner
If you find a post helpful and are logged in the Web interface, please
show your appreciation by clicking on the star below. Thanks!

Andy of Konecny Consulting in Toronto
Knowledge Partner Profile
If you find a post helpful, click the Like button below. Thanks!
davidkrotil Super Contributor.
Super Contributor.

Re: Performance guide?

10 messages / s is very good speed, not sure how many messages do you archive per job if this speed is issue for you. Only what you can do is not archive if your POA is something doing ( QF, gwcheck ... ), second tuning tip is give your Retain Server plenty of RAM, there is very good sizing guide in documentation, last tip monitor your I/O, are there many IOwaits on your CPU.
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.