Is there anything at all we can do to speed this up? With Cognos 10 BI Server it would take a long time to stop or start but nothing like this (4 minutes seemed a slow one back then). I'm happy with the stop, it's now around 30 seconds. But start is taking a bit over 10 minutes. We're on RHEL 7.6.
/opt/ibm/cognos/analytics/bin64/cogconfig.sh -stop (34 seconds last test)
/opt/ibm/cognos/analytics/bin64/cogconfig.sh -s (10 minutes 4 seconds last test)
Thanks in advance for any guidance you can give me!
No comments at all? Am I in the right place? Does this amount of time seem normal to everyone?
Quote from: stonkers on 23 Jul 2019 11:14:41 AM
Is there anything at all we can do to speed this up? With Cognos 10 BI Server it would take a long time to stop or start but nothing like this (4 minutes seemed a slow one back then). I'm happy with the stop, it's now around 30 seconds. But start is taking a bit over 10 minutes. We're on RHEL 7.6.
/opt/ibm/cognos/analytics/bin64/cogconfig.sh -stop (34 seconds last test)
/opt/ibm/cognos/analytics/bin64/cogconfig.sh -s (10 minutes 4 seconds last test)
Thanks in advance for any guidance you can give me!
Hi,
I would expect the startup to be a little slower as there are now more microservices to fire up under the covers. Ten minutes does sound slow, though. What size is your java memory set to be? Do you have the same pool size settings for the Query Service as you did in Cognos 10? One other possibility if you're using a DB2 content store is a java mismatch:
https://www.ibm.com/support/knowledgecenter/en/SSEP7J_11.1.0/com.ibm.swg.ba.cognos.tg_bitshoot.doc/t_c8servicedoesnotstartorfailsafterstarting.html#C8ServiceDoesNotStartorFailsAfterStarting
I'd expect to see the instance failing with this issue, though.
Cheers!
MF.
Hmmm, checked the memory and it's set to 4096. I'll adjust to 1152 and see what that does to startup. Thanks!
Uhhh, no, 4096 is way bigger than 1152, that would be dumb...
Quote from: stonkers on 13 Aug 2019 08:03:28 AM
Uhhh, no, 4096 is way bigger than 1152, that would be dumb...
The java memory size in the main config definitely affects startup time - the higher you set it, the longer the service takes to start. What did you have it set to in your Cognos 10 instance? If you set it to the same value in your CA instance, do you see similar startup time?
MF.
So I changed it to 1152 and it acts like it started in 30 seconds, which would be fabulous, but it never starts. We run on port 9300 and it never LISTENS there after the start command. Not sure where to go from here...
nm, figured that out, CS was offline. Will continue tests and report findings.
OK:
4096: stop :33 start 10:04
1152: stop :26 start 8:10
1536: stop :24 start 7:40
Still really slow, should I go higher?
Tried 2304, time went up to 7:56. So we'll do performance testing on 1536 for running reports in relationship to the 4096 that we had before. I'm the only one who really benefits form the startup time, lol...