Title: Extremely large wp_fvm_cache table
Last modified: February 17, 2021

---

# Extremely large wp_fvm_cache table

 *  Resolved [dimashelikhov](https://wordpress.org/support/users/dimashelikhov/)
 * (@dimashelikhov)
 * [5 years, 3 months ago](https://wordpress.org/support/topic/extremely-large-wp_fvm_cache-table/)
 * Hello,
 * We noticed a large wp_fvm_cache table. Could you recommend a safe method to clean
   up the table and prevent the issue from happening?
 *     ```
       +----------------------------------+------------+-------------+--------------+------------+
       | TABLE_NAME                       | table_rows | data_length | index_length | Size in MB |
       +----------------------------------+------------+-------------+--------------+------------+
       | wp_fvm_cache                     |      73690 | 17317888000 |     12140544 |   16527.20 |
       ```
   

Viewing 1 replies (of 1 total)

 *  Plugin Author [Raul P.](https://wordpress.org/support/users/alignak/)
 * (@alignak)
 * [5 years, 3 months ago](https://wordpress.org/support/topic/extremely-large-wp_fvm_cache-table/#post-14065014)
 * If you are able to inspect some of the rows via phpmyadmin or some other tool,
   you can look for the meta column and see if the same url keeps getting minified
   there.
 * Unless your site has at least 50k posts and each post has it’s own different 
   set of css or js code, most likely, you have 1 or several css or js files that
   are dynamic in nature, so for every pageview, that url may be changing.
 * The contents on CSS or JS files should not be changing on every pageview, so 
   disable FVM and check which plugin or code is doing it and why. There is likely
   some dynamic css or js fle somewhere, which you should exclude from merging on
   FVM, else, it’s going to detect a new file every single pageview and generate
   a new cache on the database.
 * Note it’s perfectly safe to truncate (delete) the wp_fvm_cache contents programmatically
   and periodically, or manually via wp-admin as well.
 * However, you should really check which files do you have that are causing this.
   
   A few plugins use anonymous class names, so the content changes on every pageview.
 * You can for now empty that table, but FVM will start filling it again as the 
   issue causing it is still there.

Viewing 1 replies (of 1 total)

The topic ‘Extremely large wp_fvm_cache table’ is closed to new replies.

 * ![](https://ps.w.org/fast-velocity-minify/assets/icon-128x128.jpg?rev=1440946)
 * [Fast Velocity Minify](https://wordpress.org/plugins/fast-velocity-minify/)
 * [Support Threads](https://wordpress.org/support/plugin/fast-velocity-minify/)
 * [Active Topics](https://wordpress.org/support/plugin/fast-velocity-minify/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/fast-velocity-minify/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/fast-velocity-minify/reviews/)

 * 1 reply
 * 2 participants
 * Last reply from: [Raul P.](https://wordpress.org/support/users/alignak/)
 * Last activity: [5 years, 3 months ago](https://wordpress.org/support/topic/extremely-large-wp_fvm_cache-table/#post-14065014)
 * Status: resolved