<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://sugarclub.sugarcrm.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Performance Issues with Custom Table Joins and Sorting in SugarCRM After MySQL Upgrade to 8.0.41</title><link>https://sugarclub.sugarcrm.com/dev-club/f/questions-answers/8063/performance-issues-with-custom-table-joins-and-sorting-in-sugarcrm-after-mysql-upgrade-to-8-0-41</link><description>We recently upgraded MySQL from version 5.7 to 8.0.41. Post-upgrade, we have observed a noticeable improvement in overall query performance. However, we are encountering a significant performance issue, specifically when accessing list views in modules</description><dc:language>en-US</dc:language><generator>Telligent Community 12</generator><item><title>RE: Performance Issues with Custom Table Joins and Sorting in SugarCRM After MySQL Upgrade to 8.0.41</title><link>https://sugarclub.sugarcrm.com/thread/32988?ContentTypeID=1</link><pubDate>Tue, 08 Apr 2025 08:29:45 GMT</pubDate><guid isPermaLink="false">5c521d64-519d-47a6-9065-134618b211bf:96a0ca86-e208-402d-80dd-f9f7e8dfdb33</guid><dc:creator>DHIRENDRA KUMAR</dc:creator><description>&lt;p&gt;Hey Suraj,&lt;br /&gt;&lt;br /&gt;I am facing the same issue in both SugarCRM versions 13.x and 14.x.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Performance Issues with Custom Table Joins and Sorting in SugarCRM After MySQL Upgrade to 8.0.41</title><link>https://sugarclub.sugarcrm.com/thread/32987?ContentTypeID=1</link><pubDate>Tue, 08 Apr 2025 08:27:37 GMT</pubDate><guid isPermaLink="false">5c521d64-519d-47a6-9065-134618b211bf:d073fecf-ccf1-4b6c-89b7-2c33ce191395</guid><dc:creator>Suraj Kumar</dc:creator><description>&lt;p&gt;Hi Dhirendra,&amp;nbsp;&lt;br /&gt;Are you using upgraded version of Sugarcrm?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Performance Issues with Custom Table Joins and Sorting in SugarCRM After MySQL Upgrade to 8.0.41</title><link>https://sugarclub.sugarcrm.com/thread/32986?ContentTypeID=1</link><pubDate>Tue, 08 Apr 2025 08:24:43 GMT</pubDate><guid isPermaLink="false">5c521d64-519d-47a6-9065-134618b211bf:30656604-cd76-4c64-a8d0-e835b86b7244</guid><dc:creator>DHIRENDRA KUMAR</dc:creator><description>&lt;p&gt;Hey &lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;a class="internal-link view-user-profile" href="/members/liamh"&gt;Liam Hastings&lt;/a&gt;,&lt;/p&gt;
&lt;p class="" data-start="47" data-end="146"&gt;We&amp;#39;ve already tried the same, and with MySQL 5.7, it works faster. Yes, if I remove the following:&lt;/p&gt;
&lt;p class="" data-start="148" data-end="213"&gt;&lt;code data-start="148" data-end="213"&gt;ORDER BY leads_cstm.last_call_date_c DESC, leads_cstm.id_c DESC&lt;/code&gt;&lt;/p&gt;
&lt;p class="" data-start="215" data-end="303"&gt;it performs better, I know this part, but we need this. However, as you know, we need this for the UI list view in SugarCRM.&lt;/p&gt;
&lt;p class="" data-start="305" data-end="441"&gt;I reviewed the query with&amp;nbsp;&lt;code data-start="331" data-end="340"&gt;EXPLAIN&lt;/code&gt;, and it is not using the same index. Unfortunately, we cannot force the use of that specific index.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: i have upgraded mysql 5.7 to mysql 8.0.41</title><link>https://sugarclub.sugarcrm.com/thread/32985?ContentTypeID=1</link><pubDate>Tue, 08 Apr 2025 08:19:27 GMT</pubDate><guid isPermaLink="false">5c521d64-519d-47a6-9065-134618b211bf:8dd492f3-61bb-41d6-aa6c-605605fc7e46</guid><dc:creator>Liam Hastings</dc:creator><description>&lt;p&gt;&lt;a href="/members/dhirendrakumar332183"&gt;DHIRENDRA KUMAR&lt;/a&gt;&amp;nbsp; You might find you just need to add a custom index to the leads_cstm.last_call_date_c field. I suspect if you run the query without the order by it is probably fast. Running an EXPLAIN on that query will highlight if it is failing to use an indexes&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>