Best practice.....setting Affinity info

[cognosguru]

Hello All,

Since every time I call Cognos support I get a different answer I thought I would ask the people in the know.  What is the best setting for High Affinity, Low Affinity, and # of Processes for both batch and interactive? (we have 2 CPU's)

Any and all ideas are very welcome.

Thanks,

[cognosfreelancer]

All this applies for interactive processes only viz. report service

1) I go above and beyond the thumb rule of 2 processes per CPU. I have 16 processes for a 4 CPU machine. The CPUs were getting spiked less often with max of 16 processes than with 8. Moreover some of the reports take a minute or so to run in the database. This is why we can afford the 16 processes.

2) I left the total number of affinity connections per process at 5. This is the recommended limit by Cognos.While most of our reports are HTML implying high affinity I have more low affinity connections than high. I would rather not have connections tied up.

3) I have allocated 1 GB RAM to the heap memory of our J2EE server.

We really have not focussed much on batch reporting right now.

Settings for the interactive processes are working quite fine though we are still load testing to fine tune performance.

That is the problem with performance tuning..even one new report can throw things astray.

HTH
NKT

[cognosguru]

Thanks.  We will try that.