This question is the next step in my project of Optimizing a folder/directory of images and making sure not to re-optimize an image that has already been optimized without moving the optimized image to a new directory. I had a question posted here How to avoid Optimizing images that are already optimized with PHP?
My application is a Command line tool written in PHP that wraps around several Image Optimization tools and recursively scans a supplied directory and runs ALL images through the appropriate optimizer program.
Right now if I had a folder which contained 200 images and I ran my application, it would try to optimize all 200 images which is very time consuming. So say I add another 5 images to my project and I need to run the application again, it would now optimize all 205 images instead of just the 5 new images. That is the problem I am trying to solve. My idea is to have some sort of file/DB that sits in the image folders and when my application is ran, it will first read in all images that are in this file, if the image is in this file then it has already been optimized and we do not need to re-optimize it. So in my example only the 5 new images would be ran as they would not be in the file. Once completed, these 5 new images would be merged into this file so on the 3rd run of my application all 205 images would be skipped as they have already been optimized and added to the file/DB.
I think this would be a pretty good method, performance wise but I am open to all ideas for a better way or even improvements to my current idea?
Some issue though to think about, since my application runs a supplied directory recursively, if I have a folder that has 20 images and 8 other sub-folders and these all have images and some of these sub-folders have sub-folders as well, then all the images under the root supplied folder are ran, regardless of how deep it is in the hierarchy. So I am not sure if I would need to have a separate file/DB under each sub-folder that list the files processed already under each sub-folder or if 1 file/DB under the root folder would be good enough as long as it had the file path relative to the root folder.
Other thoughts are, if an image is deleted, do I need to somehow remove it from this file/DB or should I just not bother as it will likely not affect anything anyways?
My main question here, does this sound like a good solution? A file or Database type file in the image folder to list the files already optimized? If you think it is, how should I go about creating this file, should it be a simple text file with 1 image file with path on each line, or an XML file or what kind of file, PHP will likely have to read this files content into memory as an array and then when recursively scanning my directories of images it will have to compare each image it finds with this Image List array to verify if it is already in the processed list or not and then build a list of un-processed files and then process just those files
Please share your thoughts, suggestions, critism, etc, I have never done anything like this
It is a good idea and in general terms called cataloguing.
Couple of things I will do is to
Also I can do another thing which could be a overkill but manageable.
Say you have your images in a folder lets call it “incoming” or “databucket” when you end up optimizing your images you can then move them to another folder called say “outgoing” or “filesystem” and deleting them from incoming.