Optimize Logic Hooks and API Response Time

Can you provide more information about your use case? Without additional details we would not be able to provide you with best practices.

Can you provide your code?

if you don’t need the information in real-time, you can invoke a SchedulerJob to perform your actions.

Hello,

There are 2 approches possible (that I can see) to advance in your optimisation process: 

1. Profile your Sugar instance to try to identify bottlenecks in your code. For this you can use XHProf : https://support.sugarcrm.com/documentation/sugar_developer/sugar_developer_guide_13.3/architecture/performance_tuning/php_profiling/ or other tools like https://newrelic.com/ (https://support.sugarcrm.com/documentation/sugar_developer/sugar_developer_guide_14.0/architecture/performance_tuning/integrating_sugar_with_new_relic_apm_for_performance_management/) or https://www.blackfire.io/

and then try and fix the code so that is runs faster.

2. If your profiling option didn't solve the issue as the process is still slow and cannot be optimised further, you can try to isolate the code that takes a long time to process and push it into a Cron Job. This will have the effect of delaying the result of the process in time (because it will be executed by the cron every minute and not imediately) but you should see a marked improvement in overall user exeperience as you replace a time consuming code with the creation of a simple SugarBean. This approach is not applicable everywhere however as some processes need an imediate result... Have a look here for Scheduler Job use: https://support.sugarcrm.com/documentation/unsupported_versions/sugar_13.1/sugar_developer_guide_13.1/architecture/job_queue/jobs/

Hope this helps.

Kind regards,

V.

Hello Krishna,

Thank you for bringing this up!

Both Jeff and Vlad's comments are spot on. Profiling your actions to identify bottlenecks is a great start, and offloading logic to the schedulers is a common approach to reduce processing time for users.

Additionally, I recommend using SugarCRM to log slow queries and focus on optimizing them in the database, adding indexes where necessary.

Regarding your mention of loading relationships, I’d like to add something specific to that scenario. In my daily work, I often see developers fetching related bean objects, even if they only need the related record ID to perform an update. 

If you identify such scenarios in your codebase, a more efficient approach would be to retrieve the related IDs using SugarQuery.
Here’s a code snippet that can be adapted to retrieve IDs:

Retrieving a Bean by Unique Field

After obtaining the IDs, you can then fetch the bean and perform the required updates like so:

Updating a Bean

The advantage of this approach is that you maintain record-level security using SugarQuery while performing only a single query to the database to fetch the IDs of the related records, instead of loading the full related bean object.

I hope this helps with your scenario.

Cheers,

André