When the plugin optimizes image processing, does it occupy server memory, or wil

  • Resolved jason2021168

    (@jason2021168)


    4 years, 1 month ago

    When the plugin optimizes image processing, does it occupy server memory, or will it be optimized on the Smush server?
    My current website has 13,000 images, how much time will it take to optimize, and how much memory will it take up on my server? I’m worried about crashing the server.

    The page I need help with: [log in to see the link]

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Support Laura – WPMU DEV Support

    (@wpmudev-support8)

    4 years, 1 month ago

    Hi @jason2021168

    I hope you’re well today and thank you for your question!

    The optimization itself is done on our servers so processing images doesn’t require resources of your server.

    However, the entire process may and will use site’s resources anyway. This is because plugin must

    – read information about each image from site’s database
    – read all the related image files from server and send them via API to our optimization app
    – the retrieve optimized images
    – save them to your server
    – and update data in DB

    Depending on the site and media library content, it may mean quite a lot of disk read/write operations and DB queries.

    13 000 images isn’t small amount but I do not know how many images there really are. Note that if you see e.g 100 images in Media Library, in reality that will be close to 400 image files on default setup and on some setups may be many more.

    This is because whenever you upload image to your site, your WordPress creates additional copies of it in multiple sites. By default there’s an original image and 3 smaller images (sometimes additional big image if original uploaded is really huge) but plugins and themes may register additional image sizes, increasing the real number of files generated per each uploaded images.

    So I’d say with 13 000 images there’s probably around at least 50 000 image files to be read, sent to our API, fetched back and saved to server; maybe more if theme/plugins added additional sizes.

    While I understand your concerns about memory usage and time, I’m afraid I cannot really estimate any of them. The number of images won’t really affect memory usage much but it surely will affect optimization time. Yet, I can’t tell how long it will be because it depends on how fast your site/server is (in terms of reading writing files and data in db), how fast your site’s connection is, how big are these images, what is the current (at any given moment) “load” on our end and so on…

    Basically, the more image and image sizes, and the bigger images are, the more time it will take.

    Kind regards,
    Adam

    Plugin Support Nithin – WPMU DEV Support

    (@wpmudevsupport11)

    4 years ago

    Hi @jason2021168,

    Since we haven’t heard from you for a while. I’ll mark this thread as resolved for now. Please feel free to re-open the thread if you need further assistance.

    Best Regards
    Nithin

    ezedomb

    (@ezedomb)

    4 years ago

    Hi. The plug in just created a lot of different varieties of image sizes.
    How I could reduce that. I remember seeing checkboxes but I don’t know where in the configuration.

    Could you help me please

    Ezequiel Domb

    Plugin Support Laura – WPMU DEV Support

    (@wpmudev-support8)

    4 years ago

    Hi @ezedomb

    Smush does not add any additional image size to the site and it doesn’t create additional images.

    The only two tools that could possibly create image files are Local WebP (which is a Pro feature) and the “Backup uploaded images” option in Bulk Smush setting. But that option wouldn’t create additional sizes but just make a single backup file (with .bak in filename) of original files.

    If you see multiple images in various sizes, those image sizes must have already been registered on site by theme and/or other plugins.

    You can stop Smush from compressing them by selecting image sizes under the “Image Sizes” (if you switch it to “Custom”) on “Smush -> Bulk Smush” page. Those would be “checkboxes” that you mentioned.

    But it won’t prevent image creation. To stop that you would need to remove (“unregister”) any image sizes that you don’t need. Usually that’s a matter of theme options and/or plugin settings but not always can be directly changed (not always there’s option available).

    You can use this free plugin to sort it out then:

    https://ww.wp.xz.cn/plugins/image-sizes/

    I think this should do the trick:

    – install and enable this plugin first
    – go to “Media -> Image Sizes -> Disable Thumbnails”
    – disable all the image sizes that you don’t want/need to use there and save settings

    – go to “Smush -> Bulk Smush” page and switch “Image sizes” option from “All” to “Custom”
    – also disable checkboxes for the same image sizes (so Smush wouldn’t process them)

    – go back to “Media -> Image Sizes” page and use “Regenerate” option

    – get back to “Smush -> Bulk smush” and bulk smush images again

    It may not entirely ‘clean up’ already existing images (you can use free Media Cleaner plugin for that, I believe) but it should prevent generation of images in any unnecessary sizes in future.

    Note: I strongly recommend taking full backup of the site before attempting any of that, just to stay on a safe side.

    Kind regards,
    Adam

Viewing 4 replies - 1 through 4 (of 4 total)

The topic ‘When the plugin optimizes image processing, does it occupy server memory, or wil’ is closed to new replies.