• Resolved enesc

    (@enesc)


    # Query 5: 0.00 QPS, 0.01x concurrency, ID 0x3A74716EEFE412929F822B824CE0E786 at byte 37750744
    # This item is included in the report because it matches --limit.
    # Scores: V/M = 0.02
    # Time range: 2025-06-18 10:22:43 to 2025-07-01 14:32:11
    # Attribute pct total min max avg 95% stddev median
    # ============ === ======= ======= ======= ======= ======= ======= =======
    # Count 4 2234
    # Exec time 5 12529s 5s 14s 6s 6s 368ms 5s
    # Lock time 1 171ms 30us 219us 76us 113us 23us 76us
    # Rows sent 68 4.87G 2.19M 2.27M 2.23M 2.26M 42.05k 2.15M
    # Rows examine 38 9.75G 4.38M 4.55M 4.47M 4.47M 84.11k 4.47M
    # Rows affecte 0 0 0 0 0 0 0 0
    # Bytes sent 74 1.35T 623.75M 647.10M 635.87M 617.62M 0 617.62M
    # Query size 0 150.53k 69 69 69 69 0 69
    # String:
    # Databases xxx
    # Hosts localhost
    # Users xxx
    # Query_time distribution
    # 1us
    # 10us
    # 100us
    # 1ms
    # 10ms
    # 100ms
    # 1s ################################################################
    # 10s+ #
    # Tables
    # SHOW TABLE STATUS FROM
    xxx LIKE 'wp_wpdm_visitors'\G
    # SHOW CREATE TABLE xxx.wp_wpdm_visitors\G
    # EXPLAIN /*!50100 PARTITIONS*/
    SELECT * FROM wp_wpdm_visitors WHERE ID >= 0 ORDER BY created_at DESC\G
    # 22.9s user time, 170ms system time, 72.10M rss, 346.82M vsz
    # Current date: Tue Jul 1 14:32:30 2025
    # Hostname: xxx
    # Files: /var/log/mysql/slow-query.log
    # Overall: 45.29k total, 227 unique, 0.04 QPS, 0.19x concurrency _________
    # Time range: 2025-06-18 10:22:43 to 2025-07-01 14:32:11
    # Attribute total min max avg 95% stddev median
    # ============ ======= ======= ======= ======= ======= ======= =======
    # Exec time 216550s 1s 142s 5s 7s 3s 5s
    # Lock time 11s 0 3s 240us 194us 16ms 93us
    # Rows sent 7.08G 0 27.13M 163.98k 2.15M 972.20k 3.89
    # Rows examine 25.55G 0 27.13M 591.49k 4.26M 1.29M 222.42k
    # Rows affecte 3.91M 0 322.03k 90.54 0 3.27k 0
    # Bytes sent 1.81T 0 12.60G 41.91M 617.62M 276.29M 118.34
    # Query size 99.86M 6 2.03M 2.26k 2.27k 36.83k 918.49

    # Profile
    # Rank Query ID Response time Calls R/Call
    # ==== =================================== ================ ===== ========
    # 1 0x6913E1E442724881E3B85E9AFC885653 46715.0042 21.6% 9674 4.8289 0.22 SELECT wp_posts
    # 2 0xE0D4AB0BE98060BD7B1BF12036A606B5 42613.1716 19.7% 7514 5.6712 0.12 SELECT wp_posts
    # 3 0xFF02A83B16BCC23977D0218235E5B9DE 28352.8860 13.1% 4732 5.9917 0.17 SELECT wp_posts
    # 4 0xCFFC7C304166AEE980B2CA58B7A88417 16539.0603 7.6% 2633 6.2815 0.20 SELECT wp_posts
    # 5 0x3A74716EEFE412929F822B824CE0E786 12528.5934 5.8% 2234 5.6081 0.02 SELECT wp_wpdm_visitors

    As you can see wp_wpdm_visitors is very big and slow for us. Can you release a fix for that issue please?

    The page I need help with: [log in to see the link]

Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Support Md. Ibrahim Khalil

    (@mdibrahimk48)

    We’re currently investigating the issue and will get back to you soon with an update.
    Thanks for your patience!

    Plugin Support Md. Ibrahim Khalil

    (@mdibrahimk48)

    Each time someone visits your website, a log entry is recorded in the analytics table. This is part of our optimized tracking system.

    If you prefer not to store these logs, you can simply disable Dark Mode Analytics from the plugin settings. This will stop the logging process entirely.

    Thread Starter enesc

    (@enesc)

    @mdibrahimk48 I already disabled it but it still recording these logs.

    Thread Starter enesc

    (@enesc)

    @mdibrahimk48 it’s not resolved. I already disabled “Dark Mode Analytics” setting 1 week ago but still table gets some data. Can you fix this issue or optimize that table please?

    Plugin Support Md. Ibrahim Khalil

    (@mdibrahimk48)

    Thanks for your reply!

    We’re currently investigating the issue and will get back to you soon with an update.
    Thanks for your patience!

    Plugin Support Md. Ibrahim Khalil

    (@mdibrahimk48)

    We’ve released a new version v5.2.12 which includes a fix for this issue.
    Please update your plugin to the latest version and check again.

    If you face any further issues, let us know. We will help you!

Viewing 6 replies - 1 through 6 (of 6 total)

The topic ‘Optimize wp_wpdm_visitors table’ is closed to new replies.