How do I optimize Gallery 2?

Gallery 2 Optimization

Gallery, the open source web based photo album organizer, offers you an easy way to manage your photos on your website. This article will explain how to configure Gallery 2 to deliver content more effectively to your website’s visitors.

The steps below are best practices and have been tested and verified to optimize your Gallery 2 application.

Step 1

Disable FollowSymLinks (Apache) on your web server.

Step 2

In Gallery 2, navigate to the Site Admin > Performance tab and enable “Max Acceleration.” This will cache page views and result in a significant speedup on websites where the content does not change often. Please note this feature does not always speed up Gallery 2. Disable if necessary.

Step 3

After massive changes, optimize the database (Site Admin -> Maintenance)

Step 4

Avoid using too many useralbums. This is a shortcoming of the current permission architecture of Gallery 2; it has challenges scaling with the number of ACL IDs (the more unique permissions you have for various items/albums, the more ACL IDs you will have). This will be corrected soon.

Step 5

Use the locking type that is faster for your server found under Site Admin -> General). Usually, this is file based locking (flock) and not database based locking.

Step 6

Avoid adding too many blocks to your pages. Each block loads its own data and the more stuff you add to your page, the higher the complexity of each request.


Some modules don't scale as well as others. Here is a brief explanation of what these modules do and some warnings:

-randomhighlight - Don't use small delays. Gallery has to generate the thumbnails on-the-fly when the randomhighlight timeout is reached.

-captcha - Good for your performance. It not only prevents comment spam, but should block comment spam attacks early in the process thus blocking additional requests. This should compensate for the dynamically generated captcha challenge images.

-zipcart - Excessive use of zip downloads are also pretty CPU intensive.

-slideshow - can be CPU intensive if search bots are hitting it. Disable it or use robots.txt to block search engines from hitting it.

© 2015 Rackspace US, Inc.

Except where otherwise noted, content on this site is licensed under a Creative Commons Attribution-NonCommercial-NoDerivs 3.0 Unported License

See license specifics and DISCLAIMER