Hi,

at a coustermers invirnonment we have enormous performance issues while login process. most of the time it takes round about 1 - 2 minutes until the users se the welcome page.

we already have checked the log of slxprofiler, we worked through the iis performance tips for iis, we traced sql statements... etc. but we don't get the bottleneck.

i now that there is the possibility to add indexes to the database, but without any idea what the problem itselve is we can't really do that.

so do you have some tips for us to get that problem solved? the users are very unhappy.

The portal is an SLX 7.5.4 with Web HF 3.

Sebastian:

  Is your Site Pre-Compiled?

  When the request comes in, what process spikes the CPU on the Server?

  If the site is not pre-compiled, you would see a lot of time spent by the Compiler (csc.exe), and once the site is compiled, it is then served.

  Next thing may be Implementing Compression (as long as you have enough resources server side), as this may alliviate some of the Network Issues (Latency) as you put less bytes on the wire.

  There are indeed many other variables to look into, and it seems as if you have already looked into a few, but you may need to do some further troubleshooting. I would doubt that the problem is exclusively coming from SQL Performance.

  I have worked with several large Implementations of SalesLogix Web Client for over 6 years now and am have done a lot of Performance reviews (from the DB, IIS, Network and Client side). Let me know if you would like some help on this issue.

sry, that i did not mentioned that: yes, the site is pre-compiled.

point compressoin: how do i do that? iis compression is already active.

for more details i have to ask my co-worker first. he can provide further details in this case.

Are you sure that it is Pre-Compiled?

  I have ran into several customers where the App Architect Pre-Compilaton doesn't complete (even though there are no errors during the Compilation).

  The best test here is to check the Site and see if you have any .cs files. Also, within the Bin folder you would find a bunch of ".compiled" documents.

  Another way to test, as I stated, is to run TaskManager and look at the processes' CPU Utilization. Make a Request and see what process Spike.

  Also, you could use Fiddler (or a similar tool) on the Client Side to determine how long a Request takes to be completed. You may even get the time it took the Server to process the request, and the time it took the request to make it to the client. This would help you figure out if you have issues server side or on the network.

  And, if your requests do come back quickly from the Server, and with no  network issues, then it may even be a Client Rendering issue.

  Regarding Compression, you could look over the Implementation guide to figure it out. It varies depending on the version of IIS you are running.

They say "yes" so I'm to 90 % sure that is active. The compression guided by the implementation guide should be done. but i will check that.

Then next thing is to determine what part of the request is taking the longest.

The Server PRocessing, the Download (network) or the Client Rendering.

SLX Profiler:

are you absolutely certain that this isn't spinning out of control on load?

NOTHING is going after x00 rows...

.nothing has a GetRows time over 1.0000, etc?

No query is going after an unindexed field. EVER?

You are doing a full backup of SQL Server NIGHTLY with full update Statistics?

You are reindexing all indexes nightly for SQL Server.

You mentioned that you didn't have any idea where the problem is so couldn't change indexes.....

1. have you redone your indexes per Mike Strieder's performance gude? (in fact, have you gone through this guide in its entirety and setup your entire system accordingly? Be honest here!). The Index hints are crucial to loading speed.

2. Ask your user's what their favorite searches and groups are.....then make sure the fields are indexed and the SQL is correct (use IN not OR if possible, biggest filters listed first, etc.).

All tabbed form grids are using Smart Selection and EnablePages with a size under 25? That's ALL grids.

You've run Integrity Checker in the last week?

You've set BLANK Char(12) fields to NULL? Especially in the History and Activity tables.....

Activities from X years ago have been DELETED as they have no relevance.

Available RAM on the SQL Server is double the SLX Database size and you are loading the entire SalesLogix  database into RAM.

What's going on with the Welcome page and dashboards? How much stuff are you displaying that has to be loaded up each time?

We just removed a script that was running EVERY time a user went to an account .... we now run it twice a day as a console application....no more timeouts at 1.5 minutes for accounts with lots of records affected by the script.

How many users per Web Server? What else is running on the Web Server besides IIS?

Where is the SLX OLE DB Provider located? Can it be moved to the SQL Server?