APC Breaking Dropdowns

[mikesolomon]

I have started using APC to speed up Sugar

I have caching turned on for my Live & Development systems which are on the same server

I have added a couple of new dropdowns by creating a file custom/Extension/application/Ext/Language/en_us.mapping_dropdown.php

If I turn off APC caching these dropdowns work properly and are available in editview but turning on caching breaks them

Any ideas on why this is happening and how to fix it would be much appreciated

Restarting Apache seems to fix the problem but it has made me very nervous of APC

[Chris_C]

While I can't say specifically why that's happening in your case -

I recently read a technical article describing the Sugar's hosted offering, SugarOnDemand, with details on how they have configured and tuned caching on their servers - with performance graphs etc.

The takeaway from the article - they're serving many, many simultaneous users per server - with absolutely the highest speed - and total accuracy of the page.

I would recommend taking a look at the article and duplicating SugarOnDemand's caching setup on your server.

[mikesolomon]

While I can't say specifically why that's happening in your case -

I recently read a technical article describing the Sugar's hosted offering, SugarOnDemand, with details on how they have configured and tuned caching on their servers - with performance graphs etc.

The takeaway from the article - they're serving many, many simultaneous users per server - with absolutely the highest speed - and total accuracy of the page.

I would recommend taking a look at the article and duplicating SugarOnDemand's caching setup on your server.

Chris

Thanks

do you know where I can find the article?

I restarted Apache and got my drop-downs back then they disappeared again

[Chris_C]

Here's a recap of the article - not the actual article itself - but it's the same thing - written by the actual engineer in charge of sugarondemand caching using APC.

SugarCRM and Caching with APC | ckdake.com

I saw the original article on an official sugar site - sugarforge, the developers site, or the main Sugarcrm site. Sure it's out there somewhere.

You can also have a look at these - they seem to cover the same/similar ground - general performance tuning - ought to get you super fast speeds out of sugar:

» Recommendations for Tuning the Performance of Your Stack | Blog Archive | SugarCRM Knowledge Base

SugarCRM Developer Blog » Blog Archive » Some Quick Pointers on Improving SugarCRM Performance

SugarCRM: Performance Tuning - Documentation and Knowledgebase :: Omni Technology Solutions

Recommendations for Performance Tuning and Resource Planning for CRM Hosted on LAMP/WAMP. - Documentation and Knowledgebase :: Omni Technology Solutions

Post back and let us know what you end up doing for settings etc, and your speed results.

[mikesolomon]

Chris Thanks

The whole thing is beginning to make my head hurt

in SugarCRM Developer Blog » Blog Archive » Some Quick Pointers on Improving SugarCRM Performance

it says : Disable explicit caching in the app by setting ‘external_cache_disabled’ => true in config.php.

but it also says use apc - I'm confused

[Chris_C]

You would just disable it as an A/B test, or reality check.

The reason being : if it's external cache is enabled, and Sugar is getting errors connecting to the cache daemon, that itself will cause a slowdown. So disable it and see if it speeds up - that tells you sugar is having problems connecting to your cache - your cache may be misconfigured.

[mikesolomon]

You would just disable it as an A/B test, or reality check.

The reason being : if it's external cache is enabled, and Sugar is getting errors connecting to the cache daemon, that itself will cause a slowdown. So disable it and see if it speeds up - that tells you sugar is having problems connecting to your cache - your cache may be misconfigured.

I guess that makes sense

I think I'm going to need to talk to sugar and see what they advise

APC is definitely speeding up Sugar but I am getting some weirdnesses

[jmertic]

The issue is that in older versions of Sugar, we didn't properly reset the APC cache keys ( or the cache keys for any used external cache ) when the data was changed. This should work much now in Sugar 6.3 and later.

[mikesolomon]

The issue is that in older versions of Sugar, we didn't properly reset the APC cache keys ( or the cache keys for any used external cache ) when the data was changed. This should work much now in Sugar 6.3 and later.

That makes sense

is there anyway to make it work with 5.5.1?

[Chris_C]

To get those fixes for 5.5.1 you'd need to pay a sugar dev to backport the changes from 6.3 to 5.5.1.