Navigating around Info Desktop very slow

[amurgett]

We have 2 APS (clustered), 6 Info servers and about 400 jobs run per day.

During the day things can slow down to an unacceptable level, i.e. trying to open a folder on the Info desktop really can take 10 minutes.

What is causing this ?

Could it be the APS too busy in their scheduling role and not spending enough time on their Info Desktop controlling role?

If this is the case, can I instruct one APS to be scheduler only and the other to satisfy the Info Users requests only ?

Any ideas ?

 

[rhinok]

That's not exactly how it works. The Info Desktop is a client-side application that is basically making calls to the Info System Database based on your User ID and Permissions.

The desktop can slow down considerably if your Info System Database is overtaxed (as you've questioned), corrupt or too large (mostly applicable to MS Access).

The desktop can also slow down based on inefficient Desktop design. For example, one of my clients had a Top Level Folder for a specific report group. Within that Top Level Folder were up to 70 sub-folders specific to only 1 report, each! This is horribly inefficient and takes up way too much space in the Info Sytem Database.

Desktop design isn't limited to just the Folder/Report design either. User Groups are also another factor. Do all users need access to all reports? Desktop access can be accelerated greatly when Users see a limited Report structure, based on their individual permissions.

Hope this helps

 

[Nuffsaid]

Hi,

I agree with rhinok, structure is important, but traffic can also slow down the system. 400 reports a day? Are all being scheduled during the day when your network is working at "Full Capacitey"? Would it not be more practical to run reports over night when there is little or no system demand?
How many users access Info on a typical day? What type of "Hardware" is powering your APS, Job and Viewing servers?

Just some thoughts....

Nuffsaid.

 

[amurgett]

Dear rhinok and Nuffsaid

Cheers for the replies. The desktop folder design is we use in my opinion is fine, user permissions are used however I am interested in what you said about the Info database (ours is on Oracle) being too large or corrupt. There are 8000 rows in the ci_runtimeimage table and 3700 rows in the ci_infoobjects table, not excessive in my opinion but these tables have no indexes, is this right ?

As for corruption, as the problem is only really the long delay regarding desktop navigation surely corruption can be ruled out also ?

Now Rhinok, regarding 'network capacity', our reports are scheduled in a tiered fashion so that you don't get too many reports running at the same time. 6 is probably average. These reports are run overnight, starting at 3am.

Going back to my original point, do you know any way of instructing one of the APS to have a primary role of assisting with desktop navigation ?

 

[AllyPen]

I had something like this. Once I moved Info DB from Access to SQL server, it disappeared