Gallery Causing Server issues

Hello,

I was using Gallery 1.4 and my hosting provider shut down the gallery script that was eating up resources. My client said he was adding galleries and deleting some old images.

I am using Revolution 2.2.1

I decide to see what would happen so I removed 1.4 and installed Gallery 1.5.2 so I will see what happens. But I wanted to find out if anyone else is having issue?

Thank you

I'm not surprised your site got shut down. Gallery is very hard on a server, we have one client using it and their load shoots up to 25+ as soon as they start adding images. Their resources are isolated, so it's not a problem for us, but a shared environment you will get shut down.

Imagemagick will help some with the load issues, but I haven't seen Gallery running on a shared server without problems. You might check the size of the uploaded images, and consider cutting them down closer to the final output.

Do report back if 1.5.2 helps.

Any kind of image processing will be very resource-intensive. There are desktop programs that process images into the correct size and resolution, as well as adding watermarks and other features, in bulk lots that make preparing images for Web use much easier. I've used these, then in the HTML page they generate for their gallery I just chop out the gallery part and put that in my MODx resource. Upload the images to the proper directory (most of these programs have FTP capabilities so they automatically upload the images as they are processed) and it's all set.

@AMDbuilder,
shoots up to 25+, of what?

Quote from: goldsky at Aug 23, 2012, 04:24 PM

@AMDbuilder,
shoots up to 25+, of what?

The server load goes up to 25 (normal is 0.05 range).

Periodically, I think about porting MaxiGallery. AFAIK, it does much of the server-intensive image processing on upload, just once per image. I suspect that it would be much lighter than Gallery.

If my experience with NewsPublisher is any indication, though, it would take about 2 months to port MaxiGallery to Revo.


------------------------------------------------------------------------------------------
PLEASE, PLEASE specify the version of MODX you are using.
MODX info for everyone: http://bobsguides.com/modx.html

Why not just modify Gallery to process the images once on upload instead of porting MaxiGallery? Outside of the performance issues it's not a bad solution.

Not a bad idea. It might speed up a number of sites. I think it would best be done by the author, though.



------------------------------------------------------------------------------------------
PLEASE, PLEASE specify the version of MODX you are using.
MODX info for everyone: http://bobsguides.com/modx.html

The author should definitely develop some form of post upload sizing script, perhaps even tossing in a delay factor between processing images to give the server a few moments to breath.

The only problem I see with resizing the images in advance is you don't know the final sizes until the snippet call is run. Granted there are a few options, such as default image sizes using system settings (could be controlled in CMP). You could setup size groups (think tags for the album), so a user can enter their default thumbnail, slideshow, and "full" sizes, and apply them to the relevant albums.

You may generate a few more images than needed using this method, however I usually have more free disk space than CPU power. In either case some creative thinking on how to best handle what size image(s) are pre-generated would be needed.

cool feedback.
i'm porting e2g.