Learn How to fix Sugar performance problems

[mycrmspacegunnar]

The original post was removed.

The author was not authorized by his management to publish this contents here.

Clemens von Dincklage

myCRMspace
Owner

[mycrmspacegunnar]

The original post was removed.

The author was not authorized by his management to publish this contents here.

Clemens von Dincklage

myCRMspace
Owner

[lvangool]

Wow, this is very good work. thnx.

this is also very very true, the queries are horrible. The functions that construct them are quite good by the way, and I can easily understand why Sugar is the way it is. But the truth of the matter is: it's far too slow. But I have to say, if you're having 500.000 Accounts in your CRM application, you really don't want an free/open source LAMP based system. You want something bigger...That said, in the future I would make 3 changes to benchmark Sugar:

- Test with less records
- Lower the treshhold to 0.3 seconds, maybe 0.2. 1.0 is bad...mmkay?
- Test with full or default options. A listview must have a number of resulting records...otherwise you will take away a lot of functionality.

[IsOxfordDavid]

Thanks for the informative post. I have been trying to tweak my apache install to improve the speed of SugarCRM. Currently on a dual Xeon 2.8ghz with 2gb of ram and 4000 accounts I am receiving an average server response speed of 1-2 seconds. This is usable, but a little sluggish, especially when there is obviously a small rendering delay introduced by the browser as well.

If the server response could be reduced by the numbers suggested in this forum then I would consider implementation of the suggested changes a high priority.

I would also mention that there are a significant number of problems with the html, such as script appearing before the doctype declaration and mismatching td/tr tags. If the HTML does not fit W3C standards then the rendering engine has to process these errors and choose how to display the document. This has a tendency to increase the time taken for the browser to render the page.

A quick test in Firefox suggested that the total rendering of the accounts page (list set 15 records) was 3.11 secs with the server response 1.10secs. If it were possible as the above post suggests to reduce this to 0.11secs then the total rendering speed would be reduced by a third, which would have a significant impact on the end users of the system.

[lvangool]

It's true, the output of sugarCRM has some issues.

Unfortunately, I believe that Sugar's focus currently is on cool new features, AJAX implementation and interface/design. Maybe it's time Sugar spends some time and effort in upgrading the technical side of Sugar Suite. The HTML, definitions, data model, queries, and code (try to make the code easier to read by defining a code which every developer must adhere to. At the moment, indents are sometimes missing, ' and " are used together and names are not consistent.

[mycrmspacegunnar]

The original post was removed.

The author was not authorized by his management to publish this contents here.

Clemens von Dincklage

myCRMspace
Owner

[EdSawyer]

Wow, this is very good work. thnx..That said, in the future I would make 3 changes to benchmark Sugar:

- Test with less records
- Lower the treshhold to 0.3 seconds, maybe 0.2. 1.0 is bad...mmkay?
- Test with full or default options. A listview must have a number of resulting records...otherwise you will take away a lot of functionality.

Lowering the standards of the test is not really a good idea. Why? TO make the results look better? I am glad someone is finally testing this with realistically large amounts of records to show up unoptmized these queries are (which some of us have known about for a while).

Listview counts are not that useful, and a huge performance hit. They should be disabled in all cases when speed is a concern. It doesnt' remove much functionality.

agreed that a lower threshold of less than 1.0 seconds is more realistic for usability.

-Ed

[mycrmspacegunnar]

The original post was removed.

The author was not authorized by his management to publish this contents here.

Clemens von Dincklage

myCRMspace
Owner