120 second response times...

[kf6bbl2]

While clicking on random menu items such as Accounts, Contacts, Home, etc, about every forth or fifth time Sugar takes anywhere from 100 to 130 second to respond. It's not consistent, but usually close to two minutes.
Some data:
Running on the following:
Pentium dual core 3GHz, 2GB RAM, 250GB HDD with 2% used
Debian 4.0 Etch, Apache2, MySQL5.0, PHP5.2
SugarCRM Version 5.0.0f (Build 3338)
The database is basically empty, just a few dummy records I typed in.
There are no email accounts configured, and Sugar is not doing anything on a schedule, and I have not setup cron to do anything on the server.
Also when it's doing the timeout thing, I can use 'top' and there is nothing using CPU time on the server.

I turned on logging, and find the big delay here:

Thu Jul  3 09:35:35 2008,718 [18646] INFO SugarCRM - Query:SELECT * FROM outbound_email WHERE id = 'b1457e00-7ad1-e245-b65a-485d315b311b'
Thu Jul  3 09:35:35 2008,718 [18646] INFO SugarCRM - Query Execution Time:0.000112
Thu Jul  3 09:37:30 2008,656 [18659] DEBUG SugarCRM - We have an authenticated user id: 1
Thu Jul  3 09:37:30 2008,658 [18659] DEBUG SugarCRM - Retrieve User : SELECT users.* FROM users  WHERE users.id = '1'  AND users.deleted=0

Note the two minutes that went by between lines 2 and 3. I took some guesses that maybe authentication was delayed from slow DNS response or something, and the only setting I could find that might be related was this in the config.php, so I changed it:

'verify_client_ip' => false

However I still get two minute responses every fourth or fifth click of the menu items.

How do I troubleshoot this?

Thanks for any help.

[mcatling]

Hi I also get some problems like this when loading the module loader.

It takes almost 120 seconds going from each item to load, install or uninstall modules.

Checking disk io and cpu utiiisation is almost zero so it is obviously in a wait state, but I dont know how to go about identifying the problem.

Does anyone else see this behaviour?

Best regards,, Malcolm

[kuske]

Some time ago I had such a problem with a wrong .htaccess file which contained the webaddresses of my test environment.

[roblaus]

I had pretty much the same with a fresh install of 5f. I believe it's connected (at least in my case) to the fact that I was offline and Sugar wanted to talk home all the time.

[JRBurke]

I've having a similar issue when clicking around in sugar. Mostly, it's on "save" of contacts, leads and accounts. The SQL queries themselves are very fast, but something else is slowing it down.

120 seconds seems to be the "magic number" though. They all come out of the action after this period of time with the text:

Server response time: 120

I've just upgraded to 5.0.0f from 4.5.1, but everything else seems to be ok.

Fedora Core 4
php 5.2.6
mySQL client 4.1.2

[bradym80]

I am having the same problem as well...

Strangely I have noticed that I will get timeouts when connecting to sugar via mydomain.com.
When I connect via IP address directly to the machine on our network I do not have this problem.

I am not aware of how to tell the computers in my office that an internal IP is a shortcut to my domain.

I have a feeling that comcast doesnt like all that traffic loopback and perhaps puts some kind of regulation on it.

[levous]

I just installed SugarCRM CE on windows using IIS running against MS Sql Server.

The load times are inconsistent but definitely not fast enough for legitimate daily use. The page typically takes 8 seconds longer than the note at the bottom of the page indicates. The "Server response time:" varies from less than a second to more than 20 but the actual load time is rarely less than 10 seconds.

For instance, I just clicked on "Create New Opportunity" and the page note indicated: "Server response time: 2.54 seconds."
However, the icons and images took more than 20 seconds to finish loading.

Granted, I could probably have used the page after ten seconds but that is far too long to wait considering I expect early users to have to click a few times to find what they are looking for. 3 clicks at 30 seconds is not acceptable.
3 clicks at 60 is completely unmanageable.

I tried clicking on Dashboard and "Server response time: 12.48 second" but the page took more than 60 seconds to display content.

I tried to reindex tables and set content expiration on the themes and includes directory but this is not always respected.

Using Firebug, loading the "Emails" default tab, the total is:
140 requests 2.25 MB (0 b from cache) 33.8s

That is HUGE. a plain refresh results in: 39.77s

Oucharama!

[dwheeler]

For instance, I just clicked on "Create New Opportunity" and the page note indicated: "Server response time: 2.54 seconds."
However, the icons and images took more than 20 seconds to finish loading.

Once The page has loaded to that point, all the PHP calls server side have already been made, and the slowness could only be caused by either a very slow IIS server or a very slow internet connection.

Are you connected to the server locally? Do you have other content on the server to test the responsiveness with?

[levous]

Once The page has loaded to that point, all the PHP calls server side have already been made, and the slowness could only be caused by either a very slow IIS server or a very slow internet connection.

I appreciate the response but that is absolutely not true. Once the page has loaded to that point, the server side of processing is finished but all the files now need to be requested and served to the browser. Once that is completed, the page load events are fired and the client side processing begins. As I mentioned in my post, the payload on most pages is quite large. I tried to configure iis to set content expiration but most IIS veterans will attest that both browsers and IIS are not completely reliable with regards to respecting these settings. I watched the downloads using Fiddler and saw that sometimes I'd receive a 304 and sometimes a 200.

I am very excited to report a solution, and a really easy one, to this problem.

Google Chrome!

load home page after logging in
IE7: 17 seconds
Chrome: 4 seconds

Emails Tab
IE7: 35 seconds
Chrome: 7 seconds

Now, having said all this, it appears that the content expiration I set last friday is now being respected in IE because second loads of pages are much faster. go figure.

Nonetheless, I can now retract my statements that SugarCRM is not usable and recommend setting content expiration inside IIS and use Google Chrome for speedy page rendering

p.s. Sugar workd GREAT in Google Chrome

[SugarDev.net]

Is the topicstarter even sure that that configuration option is set to false?

Maybe try to run it trough the System settings screen in Config..