Extremely bad response time

[HJW]

SugarCRM version: 5.2.0k
Windows NT, IIS6

See attached file for all other info, as per PHPINFO.

My SugarCRM app is hosted by IXWeb. I recently upgraded from SugarCRM 4.5.1to 5.2.0k. Currently my response time, per screen, in between 30 and 90 seconds! And that's for every screen, and I am the ONLY user at the moment. I have research and put in some of the optimization tips on the forums, but to no avail. Because I have a hosted environment, there is little I can do about some of the master settings.

Any help would be appreciated.

[roblaus]

One possibility: Try to switch off the automatic search for updates routine . This was the reason when we had similar response times.

[HJW]

I already have that turned off, as well as the 'Send Anonomous User Stats' is turned off. Thanks for the suggestion, though.

[roblaus]

I hate to say it but then it's most likely IIS. Sugar is known for not working very well with IIS. Very little you can do except getting yourself a trial version with another hoster and give Apache a shot.

[agcopley]

I hate to say it but then it's most likely IIS. Sugar is known for not working very well with IIS. Very little you can do except getting yourself a trial version with another hoster and give Apache a shot.

Hmmm..this is not necessarily so.
I presume your installation was running fine prior to upgrade and you have not added significantly to the data volumes?

Then you need to identify if the problem is database/application or network based.

Database:
If you have access to logs you can log long querys, there is an admin setting - clear the log and evaluate
the screens for which you are having problems. If you can compare these against a local copy of your system then all the better. Or a vanilla 5.x installation in the same web provider if possible?

Application: Compare server response times against query response times. If the difference is substantial you may be experiencing latency in the Web/PHP layer. Again compare with another instance if possible.

I ma no fan of MS or IIS but its not always their fault. My Web provider loves to tinker with my settings, makes a mess and we, the client end up advising him how to fix it!

Rgds
Andrew

[roblaus]

Of course you're right - there might be various reasons. But since there is very little action happening it's usually the web server running out of memory or getting caught in some soliloquy. The Sugar log file might give an indication if the log level is set to "info".

[kuske]

How much memory do you have?

Did you already try to take the sugarcrm directory (exept the upload directory) to the not to scan list of your virus scanner?