1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

XF 1.5 xf_bb_code_parse_cache slow queries

Discussion in 'Troubleshooting and Problems' started by Solidus, May 29, 2016.

  1. Solidus

    Solidus Well-Known Member

    Hey team.

    Why are INSERT queries into xf_bb_code_parse_cache so slow for me? Here's some examples,

    Code:
    # Query_time: 8.185672  Lock_time: 0.000034  Rows_sent: 0  Rows_examined: 0
    # Rows_affected: 2
    SET timestamp=1463953530;
    INSERT INTO xf_bb_code_parse_cache
                                                                            (content_type, content_id, parse_tree, cache_version, cache_date)
                                                                    VALUES ('post', '1090937', 'a:3:{i:0;a:4:{s:3:\"tag\";s:5:\"quote\";s:6:\"option\";s:39:\"SupaHeeroh, post: 1090935, member: 7817\";s:8:\"original\";a:2:{i:0;s:49:\"[QUOTE=$
                                                                    ON DUPLICATE KEY UPDATE parse_tree = VALUES(parse_tree),
                                                                            cache_version = VALUES(cache_version),
                                                                            cache_date = VALUES(cache_date);
    Code:
    # Query_time: 3.821292  Lock_time: 0.000020  Rows_sent: 0  Rows_examined: 0
    # Rows_affected: 2
    SET timestamp=1463952192;
    INSERT INTO xf_bb_code_parse_cache
                                                                            (content_type, content_id, parse_tree, cache_version, cache_date)
                                                                    VALUES ('post', '988044', 'a:3:{i:0;a:4:{s:3:\"tag\";s:5:\"quote\";s:6:\"option\";s:33:\"Solidus, post: 988042, member: 56\";s:8:\"original\";a:2:{i:0;s:43:\"[QUOTE=\"Solid$
                                                                    ON DUPLICATE KEY UPDATE parse_tree = VALUES(parse_tree),
                                                                            cache_version = VALUES(cache_version),
                                                                            cache_date = VALUES(cache_date);
    Code:
    # Query_time: 2.336549  Lock_time: 0.000036  Rows_sent: 0  Rows_examined: 0
    # Rows_affected: 2
    SET timestamp=1464489608;
    INSERT INTO xf_bb_code_parse_cache
                                                                            (content_type, content_id, parse_tree, cache_version, cache_date)
                                                                    VALUES ('post', '673383', 'a:1:{i:0;s:14:\"Cena fan :yay:\";}', '1464445717', '1464489555')
                                                                    ON DUPLICATE KEY UPDATE parse_tree = VALUES(parse_tree),
                                                                            cache_version = VALUES(cache_version),
                                                                            cache_date = VALUES(cache_date);
    
    Any ideas?
    The table itself is 550mb with 500,000 entries.

    Thanks.
     
  2. Slavik

    Slavik XenForo Moderator Staff Member

    We've seen this a few times, and I don't think ever got to the bottom of exactly what the issue was.

    I would just disable the cache.
     
    Solidus likes this.
  3. Solidus

    Solidus Well-Known Member

    I shall do that, thanks.
     

Share This Page