Nice idea… poor execution. Danger to your site

  • We were using this on our site, but it started running really slow. Eventually, the host shut down our site. Here is why:

    I have reviewed this issue for you, and it appears that the issue here was that multiple updates were occurring on the table “wp_wsi_splashimage”, which is over 220k rows:
    +—————-+——————–+——–+————-+
    | DB | TableName | Rows | SizeInBytes |
    +—————-+——————–+——–+————-+
    | m_wrdp1 | wp_wsi_splashimage | 227533 | 5460904 |
    | m_wrdp1 | wp_posts | 2264 | 2664400 |
    | m_wrdp1 | wp_3_postmeta | 25389 | 1877460 |
    | m_wrdp1 | wp_3_posts | 1642 | 1792356 |
    | m_wrdp1 | wp_postmeta | 20503 | 1629812 |
    +—————-+——————–+——–+————-+

    This table being altered while it was being updated was likely the problem. I have removed the restrictions, but to fix this, you may wish to have your developer clean up that splashimage table, so these operations can complete faster, and not overlap.

  • The topic ‘Nice idea… poor execution. Danger to your site’ is closed to new replies.