• I just moved my site to Media Temple last week and have received 2 notifications already that my database has been auto-scaled due to increased activity.

    I have WP Super Cache enabled with super compression, and WP Widget Cache enabled for all my widgets.

    Could someone please look at my SQL report (below) and help me figure out what it causing this? I ran a slow query report (in my Media Temple cp) too, but it found no slow queries.

    I do have a lot of plugins and am still trying to figure out which one might be causing it. I am guessing that it’s my Tabbed Widgets plugin. Could someone please have a look at my site and tell me if the tabbed widgets on my sidebar and at the bottom of each post could be the culprits even though I have the Widget Cache on for each tab? Or the Multi-Level Navigation Suckerfish plugin that generates the flyout navigation menu at the top of my page?

    Here is a link to one of my posts: http://pecuniarities.com/the-frugal-literates-guide-to-affordable-reading/161

    I received my first notification the other night when running a database backup from my admin using the backup plugin. I just deactivated that plugin as well as WP automatic update.

    I’ve also just installed the following code ` 1.
    <?php echo $wpdb->num_queries; ?> <?php _e(‘queries’); ?>. <?php timer_stop(1); ?> <?php _e(‘seconds’); ?>

    ` in my footer.php to show the number of queries and seconds it takes to load a page on my site and it’s showing the following for 2 of my post pages:

    1.37 queries. 0.519 seconds
    1.20 queries. 0.415 seconds

    I would greatly appreciate any help figuring this out. Thank you.

    1 MySQL 4.1.25-Debian_mt1 uptime 0 0:51:55 Fri Oct 24 14:05:12 2008
    2
    3 __ Key _________________________________________________________________
    4 Buffer used 334.00k of 24.00M %Used: 1.36
    5 Current 3.03M %Usage: 12.63
    6 Write hit 100.00%
    7 Read hit 99.42%
    8
    9 __ Questions ___________________________________________________________
    10 Total 6.11k 2.0/s
    11 QC Hits 3.60k 1.2/s %Total: 58.94
    12 DMS 1.46k 0.5/s 23.95
    13 Com_ 737 0.2/s 12.07
    14 COM_QUIT 327 0.1/s 5.35
    15 -Unknown 19 0.0/s 0.31
    16 Slow 0 0/s 0.00 %DMS: 0.00
    17 DMS 1.46k 0.5/s 23.95
    18 SELECT 1.31k 0.4/s 21.38 89.27
    19 UPDATE 157 0.1/s 2.57 10.73
    20 REPLACE 0 0/s 0.00 0.00
    21 DELETE 0 0/s 0.00 0.00
    22 INSERT 0 0/s 0.00 0.00
    23 Com_ 737 0.2/s 12.07
    24 set_option 307 0.1/s 5.03
    25 change_db 304 0.1/s 4.98
    26 check 85 0.0/s 1.39
    27
    28 __ SELECT and Sort _____________________________________________________
    29 Scan 16 0.0/s %SELECT: 1.23
    30 Range 160 0.1/s 12.25
    31 Full join 0 0/s 0.00
    32 Range check 0 0/s 0.00
    33 Full rng join 0 0/s 0.00
    34 Sort scan 194 0.1/s
    35 Sort range 131 0.0/s
    36 Sort mrg pass 8 0.0/s
    37
    38 __ Query Cache _________________________________________________________
    39 Memory usage 5.84M of 12.00M %Used: 48.65
    40 Block Fragmnt 0.07%
    41 Hits 3.60k 1.2/s
    42 Inserts 715 0.2/s
    43 Insrt:Prune 715:1 0.2/s
    44 Hit:Insert 5.03:1
    45
    46 __ Table Locks _________________________________________________________
    47 Waited 0 0/s %Total: 0.00
    48 Immediate 2.02k 0.6/s
    49
    50 __ Tables ______________________________________________________________
    51 Open 85 of 1024 %Cache: 8.30
    52 Opened 91 0.0/s
    53
    54 __ Connections _________________________________________________________
    55 Max used 14 of 60 %Max: 23.33
    56 Total 329 0.1/s
    57
    58 __ Created Temp ________________________________________________________
    59 Disk table 188 0.1/s
    60 Table 189 0.1/s
    61 File 20 0.0/s
    62
    63 __ Threads _____________________________________________________________
    64 Running 1 of 1
    65 Cached 3 of 4 %Hit: 95.14
    66 Created 16 0.0/s
    67 Slow 0 0/s
    68
    69 __ Aborted _____________________________________________________________
    70 Clients 0 0/s
    71 Connects 0 0/s
    72
    73 __ Bytes _______________________________________________________________
    74 Sent 64.50M 20.7k/s
    75 Received 669.08k 214.8/s

Viewing 1 replies (of 1 total)
  • minademas

    (@minademas)

    Any replies to this? I am really interested as I have the same issue! tks,

Viewing 1 replies (of 1 total)
  • The topic ‘Need help reading MYSQL report to find overloading source’ is closed to new replies.