|
Monday 03 August 2009 3:57:51 am
Binary contents such as images, videos, flash, pdf or word files are stored on the filesystem, not in the database.
Other files that eZ publish generates automatically are
- log files (rotated and then removed automatically, little risk of filling disks with those)
- cache files - depending on your site design and numbre of contents, this can grow quite big You can check out size of the individual subdirs of the 'var' directory to get a fine-grained picture. There is no use in trying to empty the cache directories, as eZ publish would try to recreate all those files immediately. Otoh deleting some contents that are not needed anymore in the site but have big binary files inside might be a good idea. You could also look at the design elements, and see if you have leftover images/flash files that are not used anymore and take up disk space (you might develop a little script that parses apache access logs to find out unused design elements) Developers often leave complete or partial backups of sites around when upgrading to new versions, those would be a good candidate for cleanup. Last but not least, you could move to a "cluster" config, where eZ Publish stores cache files and binary files in a 2nd db. It would mean having a bigger db than you most likely have now, and a slightly slower site, as mysql is not best suited to serve a lot of huge blobs all the time, and in the end the cache files would be copied over to your filesystem anyway, so the space gained would depend on the cache/storage ratio...
Principal Consultant International Business
Member of the Community Project Board
|
