Is your 6.3.0 ajax slower than without ajax?

[al3]

I just upgraded 6.2.4 to 6.3.0 on my dedicated (FreeBSD) server. I find that pulling up client records to be slower than before. I get the "loading page" pop-up for a second or two and then I get the page. When I disable ajax it speeds up.

Shouldn't ajax be faster than non-ajax?

I'm using latest Firefox on an iMac with Lion.

Thanks,

Al

[rafael.q.g@hotmail.com]

I think ajax mail goal is more to allows integrations between client (web browser) and server without pages refreshes.

Once for list view it already was loaded with page first load, there was no need to use ajax for that functionality, and now it will take more time to load once we have the animation ( loading popup) before display its results.

But in situations where many records needs to be displayed at once, all sugar page could take forever to load, and now with ajax, the entire sugar page loads faster, and the user that wants to see the list needs to wait a little more, but the users whose wants to navigate between sugar tabs don't needs to wait the list view loads completaly to start to work.

[al3]

I'm a bit confused. How does Ajax help when I click on a client name to display his page any better than without Ajax?

When I click on "John Smith" with Ajax I get a "record loading" message. Without Ajax the page loads faster.

So why is Ajax implemented for Account records and Lead records, etc.

Thanks,

Al

[mkozlov_test]

Al,

if you have really fast running instance of Sugar, AJAX UI may slow things down as it affectively creates 2 http requests instead of one.

On accounts (or any other records) that do not have a lot of related records (subpanels) simple UI may be a lot faster.

BTW, AJAX UI is an add-on, so you can disable on per module basis.

[sugar_rawb]

I'm a little confused here, in our internal testing it showed that you could navigate more than twice as fast using the ajax ui vs using the regular ui.

The one time that this won't be true is when switching in and out of the ajax ui. If you have custom modules or custom links that are generated that start the two-step loading process (first load the ajax ui code, then the module data) this will be slower than just loading records in the ajax ui. Check your server logs, if you see a lot of "action=ajaxui" and not a lot of "ajax_load=1" then this could be what is happening. Every time you see an "action=ajaxui" in your server logs that means that someone has switched in to the ajax ui, if this is happening extremely often then that would be the culprit.


Depending on your use case it may be faster to disable the AJAX UI. The primary use case I can think of where this would be true is if you are primarily navigating Sugar through external links, or through links that are not being properly rewritten. If however you are primarily navigating through SugarCRM using SugarCRM (using searches, dashlets, etc), then a drop in performance would be very unexpected.

[al3]

That may be it. I have a fairly fast dedicated server that is way under-utilized. Sometimes there are no more than two or three people accessing it (and NOT accessing SugarCRM.) Thus, I can see why AJAX might be slower if your theory is correct.

I disabled AJAX for all the modules and Sugar now runs as fast as it used to before the current upgrade.

Thank you.

Al

[al3]

When you say server logs do you mean the SugarCRM logs or the log to our actual server?

Thanks.

[sugar_rawb]

When you say server logs do you mean the SugarCRM logs or the log to our actual server?

Thanks.

I mean the actual http server logs, any time you see "action=ajaxui" that means the system is initializing the ajax ui environment, which is an extra request. When you see "ajax_load=1" that means that it is running through the ajax ui and should be sped up by the system. If you see a lot of the "action=ajaxui" and not a lot of "ajax_load=1", that means your users are constantly reloading the ajax ui environment and will definitely be hit with the performance penalty.

[al3]

I mean the actual http server logs, any time you see "action=ajaxui" that means the system is initializing the ajax ui environment, which is an extra request. When you see "ajax_load=1" that means that it is running through the ajax ui and should be sped up by the system. If you see a lot of the "action=ajaxui" and not a lot of "ajax_load=1", that means your users are constantly reloading the ajax ui environment and will definitely be hit with the performance penalty.

As you predicted, I'm seeing a lot of "action=ajaxui" in the log. In fact, that's ALL I see! There are no "ajax_load=1" instances. So what do I do to get Sugar to run "correctly" with ajax? Why am I constantly reloading the ajax UI? How do I stop it? Is there some config I need to change? (Note: I'm using Firefox on Mac OS X Lion.)

Thanks.

[sugar_rawb]

As you predicted, I'm seeing a lot of "action=ajaxui" in the log. In fact, that's ALL I see! There are no "ajax_load=1" instances. So what do I do to get Sugar to run "correctly" with ajax? Why am I constantly reloading the ajax UI? How do I stop it? Is there some config I need to change? (Note: I'm using Firefox on Mac OS X Lion.)

Thanks.

The ajax_load=1 should come at the end of the URL, a lot of times it will be posted, but if you are seeing a ton of action=ajaxui's then there is a lot of reloading of the ajax ui. How are you navigating to records inside of the application. I did a quick check and it looks like clicking links from emails will load the non-ajax version, so there is no problem there, however opening new tabs when viewing records will cause the new tab to load the ajaxui, then load the record inside of the ajaxui.

Can you describe the average workflow to me a little more so I can figure out why you are constantly reloading the ajax ui?