Hi,

When a user logs for the first time in our SLX Web 7.5.3, it takes up to 24 seconds.

Scenario:
1) recycling of IIS web site
2) I log as Admin and navigate in SLX in order to warm the website pages
3) logoff
4) log with a standard user --> it takes 24 second to see the start webpage referenced in my option

If I make a logoff, the next logon takes only 3 seconds.

Any idea?

Thanks
Charles

Is your site Pre-Compiled?  Seems to me that it isn't.

Also, keep in mind that even if it was, SLX does an "Updatable" pre-compilation, meaning not every item is pre-compiled.

Suggestions:

If you are not pre-compiling, go ahead and do so.

If you already are, but it is still taking 24 seconds, your Server is probably a bit slow. You could increase the performance a bit by manually pre-compiling the site without the Updatable flag.

Thanks for your response Raoul, I have tried but the 21 seconds were still there.

We monitored IIS with lots of tools (DebugDiag 1.1 to make a dump of the w3p.exe, Network Monitor to see the network trafic initiated by the w3p.exe), and  we discovered that the IIS SLX process (w3p.exe) calls an external URL in order to make a survey (http://www.slxsurvey.com/?ver=7.5.3&per=60&lang=fr-BE) and that this website was deactivated.

This was not the main cause: actually our w3p.exe couldn't contact the URL because the w3p.exe was enable to detect our proxy. Sage should absolutly take this pbl into account by giving the possibility to the administrator to disable the survey. We deactivated teh sruvey that by changing datas in the DB. The procedure is described below (automatic translation from French).

 After completing the loading, the w3p.exe DB will write to clarify that an attempt has already conducted survey date for the user in question.

 A new attempt will be executed during the day. This explains why the only CRM was slow at first boot everyday.

 The first time a user logs in, the CRM will specify that the next attempt DB shall be done 2 months later (and not the next day).

 This explains why this problem appeared suddenly in mid-February, two months after the start of production.

 The 21 seconds had no impact on CPU servers or bandwidth.

 Workaround:

We have tested and then applied a PLSQL script in production that specifies for each user in the DB that the next survey will be attempted in 10 years.

 Thus, the process no longer launches the IIS process of survey and 21 seconds away: So you go from 25 seconds to 4 seconds to the homepage.

It is also possible to add the proxy name in the web.config:

<system.net>
<defaultProxy>
      <proxy
         usesystemdefault="false"
         proxyaddress="http://vsscansafe1e:8080"
         bypassonlocal="true"

           />
    </defaultProxy>
</system.net> 

Charles:

  Good catch, didn't think that the Survey would create such a hassle, but in this case it was due to a Combination of the Survey and your Network configuration (restrictions).

  There is a simple way to turn off the Survey:

  - Open SalesLogix App Architect.

  - Expand your Portal(s)

  - Expand the Support Files Folder

  - Scroll to the Bottom of it and locate the "Survey.xml" file

  - Edit the Survey.xml and change the Enabled property to "False"

Also, if interested, you could play with the Survey.xml file and change the URLs to make it present your Own Surveys.

Thank you for this info Raoul, we deactivated the survey.

I think it is not normal that a CRM automatically contact an external URL... and that it causes slowness when the IIS server doens't have access to the Internet...

Charles