Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>You need to do some profiling to figure out the culprit. Magento even offers some options out of the box.<br> First, go to <em>System > Configuration > Developer</em>, and add your current public IP to the Developer Client Restriction Allowed IP's.</p> <p>Then switch to the store view scope of the store in question and turn on the profiler display in the debug section. </p> <p>Next you need to enable the profiler to collect the data. This will further slow down the site (all stores), but since it will provide you with the data you need to fix it, this temporary tradeoff will hopefully be worth it. </p> <p>There are two profilers integrated in Magento. One for PHP code, and one for DB SQL queries.</p> <p><strong>PHP Profiler</strong><br> Open the <em>index.php</em> file in the Magento root directory and remove the comment character in front of the line that calls </p> <pre><code>Varien_Profiler::enable(); </code></pre> <p>When you reload a page after enabling that call you should see a long list of profiler timers at the bottom of every page, telling you the time spent and the number of calls to each profiler section in question.</p> <p><strong>DB Profiler</strong><br> Open the file <em>app/etc/local.xml</em> and add the <code>&lt;profiler&gt;</code>node to the connection configuration.<br> </p> <pre><code>&lt;config&gt; &lt;global&gt; &lt;resources&gt; &lt;default_setup&gt; &lt;connection&gt; &lt;host&gt;&lt;![CDATA[localhost]]&gt;&lt;/host&gt; &lt;username&gt;&lt;![CDATA[xxxx]]&gt;&lt;/username&gt; &lt;password&gt;&lt;![CDATA[xxx]]&gt;&lt;/password&gt; &lt;dbname&gt;&lt;![CDATA[xxx]]&gt;&lt;/dbname&gt; &lt;active&gt;1&lt;/active&gt; &lt;!-- This is the line you need to add: --&gt; &lt;profiler&gt;true&lt;/profiler&gt; &lt;/connection&gt; &lt;/default_setup&gt; &lt;/resources&gt; &lt;/global&gt; &lt;/config&gt; </code></pre> <p>After you flush the config cache, you should also see some DB query statistics and the slowest query during that page request at the bottom of the page.</p> <p>Hopefully this will give you some insight what is slowing down the store and provide you with some data how to fix it.<br> Remember to <strong>turn off</strong> the <strong>code profiler</strong>, the <strong>SQL profiler</strong> and the <strong>profiler output</strong> after you are finished. Just turning of the output only will still have the profilers happily collecting data and slowing down the whole website.</p> <p>EDIT: The data collected by the profilers is available to, for example, create sortable spreadsheets and add custom timers. This can be helpful, but goes beyond the scope of this post. A developer familiar with Magento will be fine creating such custom modules on their own.</p>
    singulars
    1. This table or related slice is empty.
    1. POOnly 1 Magento Storefront Slow
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USVinai
    1. USVinai
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POOnly 1 Magento Storefront Slow
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. This table or related slice is empty.
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload