Hello,
We have a model with about 80,000 cells per elist slice, where the largest cube is about 40,000 cells and the total dlist items is about 1,200 items. The catch is that there are 6,000 elist items in total and we are using Active Directory to govern security and have All set for Review and View rights the whole way down the elist.
Given that this is a small model (80k cells), we would have expected it to open quickly on the users machine. Now excluding user pc spec, is there anything that we should specifically check for that will impact the end user performance?
Thanks
John
Do you have multiple e_list items enabled, and if so, how many are you opening concurrently?
Another factor could also be whether users are accessing via a dial up connection, or similar network related issues.
How much slowdown are you experiencing?
JC
Hi JC, yes we do have multiple elist items enabled, however we get poor performance with a single node. Also we are all on the one Australia wide network which is a pretty fast network.
Have you set the rights on a user basis or do you use groups from the AD to set the rights? How many rows of rights do you have? How large is the xml of the production application?
How fast does the model open directly on the server?
The model opens on the server quite quickly, say 40 seconds for a single elist item and the server is an 8 cpu box with 16 gb of RAM, which is somewhat more grunty than a user box...
Quote from: craig_karr on 04 Feb 2009 04:14:55 AM
Have you set the rights on a user basis or do you use groups from the AD to set the rights? How many rows of rights do you have? How large is the xml of the production application?
Rights are set using AD groups as the authentication source from a global AD server. There are about 50 odd rows of rights. The xml is about 14.5 Mb.
15 MB xml is quite large. I have the same problem with our models. The xml used to be around 5 MB, which opens quite quickly on a client with 512MB-1GB ram, which is the most common in our environment.
After changing log in to AD and setting the rights on a user basis, the number of rights grew from about 500 to over 3000 and now the xml is 17 MB and takes two minutes to open on a normal client. On a client with 2 GB of RAM or more, it opens in about 30-40 seconds.
I have been able to decrease the size of the xml by reducing the list of rights. I have found that the xml gets smaller if I use groups from the Cognos namespace rather than active directory.
I have a case open with Cognos, where I have asked them to comment the relationship between the xml size and the rights. With only 50 rows of rights, I would have expected that the xml would be much smaller in size. Do you have cut down models enabled in your model?
It would be very interesting if you could keep us updated, if you manage to shrink the xml/shorten the opening time of your model.
By the way I don't understand the part with your e.list. Is it 1200 items or 6000 items?
Quote from: craig_karr on 05 Feb 2009 02:28:28 AM
By the way I don't understand the part with your e.list. Is it 1200 items or 6000 items?
It is 6000 items. I made a typo when listing the total dlist, rather than elist, items.
Quote from: craig_karr on 05 Feb 2009 02:28:28 AM
Do you have cut down models enabled in your model?
No cut downs either!