MUN is not retiving .

[rahb]

Hi All,

Nice to see Cognos SDK related forum.
I am working on application  where we are creating around 4000+ reports.
To minimise the performance we are using 10 threads to create reports through Java.
We observed that some of the threads like 4-5 get hung at the time of retrieving the MUN.

I just want to know what could be the reason? Does anyone came across of such problem?

Expecting kind help.

Rahul

[xiska]

Hi

... and the cpu load is low ...

MUN - Member Unique Names - are used in OLAP or ROLAP based reports.
The issue you are facing has almost nothing to do with the SDK it is a performance issue. It only seems to be one because such a penetration test simulates at least 100 real users.

Especially ROLAP is a little performance monster.
1. According to the definition the report server is creating a sometimes really complex SQL statement.
2. The Database returns a dataset
3. The reportserver creates a temporary cube on the HDD (Cognos\c8\data\cqe\RTModels) this often creates swapping
4. The reportserver does all tasks similar to a real olap creation task
5. The reportserver queries the temporary cube
6. The gateway transfers the data to the webserver and the webserver to you

In most cases the creation is critical. If you measure the time to step 2 you will be surprised how fast you system is - lets say 5s.
Step 3 often takes more than 30s while the rest takes 3s.
Each thread simulates an user. Try it for your self with Borland Silk or webloader. It works fine with 3 users - but 5 seems to be the limit.

Some settings you may need to consider:
- Memory settings of your server
- Design: You need to know that a dimension should not extend 1:1000 (1:2^16 are possible) as this ratio increases the memoryusage extreamly - try to avoid it.
- Processes: There are many settings around performance within the portal.
-> Interactive: Number of processes for Prompts - if you have only 3 the fourth must wait
-> Data Processes, Report Processes, Affinity ... same as the one before

Try to discover which of the processes is hitting the limit.

Have fun