-
Posts
-
I tried to move an X installation from the hosting company where I created it (Dreamhost) to the host my customer uses (Gate). The DB migration failed, a very helpful Gate DBA got involved, and noticed that wp_postmeta.sql is over 45MB and the whole database is 74MB. The site only has about 325 image files (plus an 120 in the media library left over from development). The largest Essential Grid page contains 100 images. Is that a normal size for an X site with only 300 images?
Is X able to deal with that many files? That really isn’t a lot, but it sure blew the DB up in size. Load times aren’t bad given the number of images on the largest page, but I’m concerned about the DB size, and that <200MB of image files gets multiplied with additional copies in different sizes to give me an uploads directory of >850MB.
A 409KB image file (1400x930px to allow large viewing size) becomes 13 files and 1.8MB. Are all of those copies for the responsive views to increase performance by sending smaller files to smaller displays?
Standard WP implementations show which images are and are not attached to a page. X prevents that and all show unattached, so I have no way of knowing which I can delete because they’re unused. Any suggestions for that?
I plan to rebuild the site on the Gate hosting server using saved page templates; maybe that will reduce the number of images, but the DB will still be huge even at 2/3 of its current size. Am I doomed to a huge database with X theme? What can be done to optimize it?
Hi there,
Thanks for writing in! Cornerstone stores the page data separate from the final content by using post meta. So if you are using Cornerstone to build the pages then it’s usual to have such size for post meta table. It won’t affect your site performance.
Cheers!
