Wordpress LScache Plugin: Huge Litespeed Image Optimization DB table
Last Updated on: Wed, 15 Apr 2026 00:00:02 On our install Litespeed has litespeed_img_optm 207406 260562.4 KB litespeed-cache ] And Images optimized and pulled: 21019 groups (201468 images) Images previously optimized: 1120 groups (3406 images) Images failed with other errors: 1 group (8 images) Image files missing: 216 groups (2184 images) Images total: 21193 groups Why is the table size so huge? Thats almost 260MB on an 800mb DB. 1. Why is this so? 2. What happens if we decide to drop this table? The page I need help with: https://animekaizoku.com Hi, 1. Every image it optimized will have a record in database and you have over 20k images. 2. If you drop it, it may interfere some image optimization related operation , like optimization information in Media page , undo/destroy optimized images ?etc Best regards, Hi, We had Remove Original Backups under settings in ls plugin enabled from day 1. The storage optimization shows this Storage Optimization Last calculated: 07/15/2019 00:20:31 Remove Original Image Backups Last ran: 11/29/2018 09:41:55 Files: 1 Saved: 12.62K So ig there is no data that can be reversed at this point, yet this is using 250+mb to storage what it has optimized and what not? I mean, we have 4 times the info in user meta but its 5 times less in size. Isnt this supposed to store each image info and if its optimized or not? why is litespeeds table so large in size? Hi, Well , if you check the table you will see there are more info recorded in there, like origin size, optimized size, md5sum ?etc But yes, you have a good point there , many information may not needed anymore. our developers are working to improve this part on future release. Also , could you please try this query ? update wp_litespeed_img_optm set server_info= where optm_status!=notified and kindly notify us the size change ? Best regards, Hi, Ran it (After backing up the database of course) 205151 rows affected. (Query took 4.9037 seconds.) update wp_litespeed_img_optm set server_info= where optm_status!=notified We have the same size and it shows Size: 254.5 MiB Overhead: 175.4 MiB Hi, OK, then please proceed to optimize table , the overhead should be reduced. so I assume this will form 260MB down to 80MB Best regards, YEp, This is now 60mb I wonder why this isnt already included in Litespeed settings as an option to self-clean. Or Why this is isnt already self-regulating itself in the first place. Marking this as resolved as atm I satisfied with the tables current size, would wish that LiteSpeed would add something to regulate this in coming release. Hi, Thanks for the feedback. Yes, this will be added into future release. Best regards,
LiteCache Rush: Speed comes from using less, not from doing it faster
Reference