The average BO login time at our site (BO on NT against repository stored on DB2 for OS/390) used to take 27 seconds and I am still looking for perfomance and tuning hints. Since we are having approx. 200 users defined and some of these users are appearing in different groups with different authorisation attributes, the login process duration for these “complex” users increased now to an average value of 70 seconds.
What we found at our site, is the more groups a user is added to, the longer the login time is – so perhaps you need to rethink the number of groups you have set up.
Shirley Morris
Caltex Oil (SA)
______________________________ Reply Separator _________________________________
Author: Business Objects Query Tool BUSOB-L@LISTSERV.AOL.COM at INTERNET
Date: 29/10/1998 9:53 AM
Dear colleagues
The average BO login time at our site (BO on NT against repository stored on DB2 for OS/390) used to take 27 seconds and I am still looking for perfomance and tuning hints. Since we are having approx. 200 users defined and some of these users are appearing in different groups with different authorisation attributes, the login process duration for these “complex” users increased now to an average value of 70 seconds.
The average BO login time at our site (BO on NT against repository stored on DB2 for OS/390) used to take 27 seconds and I am still looking for perfomance and tuning hints. Since we are having approx. 200 users defined and some of these users are appearing in different groups with different authorisation attributes, the login process duration for these “complex” users increased now to an average value of 70 seconds.
Are there any solutions around for this problem ?
Arthur,
Just a thought, we changed from a shared file (objects.ssi) to a local file (objects.lsi) and logins got a fair bit quicker. But you may already be doing this.
I am not sure what version of BO that you are using, but I believe that is was to be resolved in 4.1.3.
There was a patch available to speed up the way Business Objects handles Group rights/restrictions when verifying a users login, and I believe it was incorporated in the latest release.
If your users are complaining about the login time, and want to use BO to run reports, etc without needing to send/retrieve from the repository, they can still do so by logging in with the OFFLINE checkbox checked. You can still use BO as normal (with your rights/restrictions intact) as long as you had logged in at least once (for a shared Objects.ssi) or once on that workstation (for a local Objects.lsi).
OFFLINE mode just prevents you from exporting and importing from (and general sending to) the repository, but all the other features remain intact.
You’re right about objects.ssi, but you win less than 1 second. Also, it depends of the number of branchs where the user is. The essential gain is adding new indexes SQL in the security repository.
Theses secondary indexes are (Sybase syntaxe to change to DB2):
create index OBJ_M_ACTOR_FK1 on OBJ_M_ACTOR (M_ACTOR_C_NAME) go
create index OBJ_M_ACTORLINK_FK1 on OBJ_M_ACTORLINK (M_ACTL_N_ACTORID) go
create index OBJ_M_RESLINK_FK1 on OBJ_M_RESLINK (M_RES_N_ACTLINKID, M_RES_N_RESTYPE)
go
create index OBJ_M_RESLINK_FK2 on OBJ_M_RESLINK (M_RES_N_RESTYPE) go
The essential new index is on M_ACTOR_C_NAME, because the login process first request is to find the user’s name in OBJ_M_ACTOR table. The 3 others indexes optimise joins.
Personnaly, on Sybase system 11 with 1200 users, I win 20% time with new indexes in security repository.
For the general supervisor : 7 seconds
For an user which is 6 times in the security domain : 12 seconds