Adding lots of images on a slow server
|
sebcool20
Joined: 2009-09-18
Posts: 41 |
Posted: Sat, 2011-01-15 21:49
|
|
Hi people, I've been using Gallery2 for a while and I just set up a new gallery using Gallery3. I'm on a pretty slow server and I've got lots of pics to add. In Gallery2, I could choose not to create thumbnails and read the files while adding them which speeded up the process, the thumbnails and resizes would be created when they were needed. I can't find the same option in Gallery3 and adding pictures takes forever. Any way to bring that feature back? Thanks |
|
Posts: 7994
Unfortunately no. The ability to defer making thumbnails in G2 required a ton of code and a PHP script in between the browser and the image requests so that we could know when you wanted an image and build it. Without that, you'll get broken images all over the place. It's cleaner and easier to always just build the image when the time comes.
We could try a slightly different approach where we stick in a placeholder and mark the image as dirty and rebuild it later, but it gets messy because (for example) modules can change the dimensions if the resize and thumbnail images so when you rebuild the image it'll change size, etc. But please file a ticket for this and we'll consider it.
---
Problems? Check gallery3/var/logs
file a bug/feature ticket | upgrade to the latest code! | hacking G3? join us on IRC!
Posts: 41
My problem here is that my host doesn't like it when I build a lot of images at once, because they other users sharing the server experience huge slowdowns... My host once called me to tell me to use less resources during a day where I had lots of visitors on my old gallery, and lots of images were being built...
So that said, the placeholder wouldn't really help on that point because I would have to build them all at once, but just later... The main point on building them when I needed them was to spread the load on the server, because it would only have to build a few pics once in a while, thus not interfering too much with other users of the same server.
I also don't really understand the point to have a good product with a lot of features (Gallery2), and then "upgrading" it to something that doesn't really does more (Gallery3), but just removes features that people used... and telling them it had been removed because it used ton of code... the code was there, why would you get rid of it if it worked? I don't know a thing in programming, I guess there are reasons to that, but upgrading to a new version that removes features and stuff the old version had seems akward to me...
Posts: 7994
You could upload the photos more slowly over a longer period of time to spread out the load, or we could use the placeholder approach and build the thumbnails/resizes slowly. Both of those approaches would take some code changes. The first one might be a little easier to implement
I think that this article does a pretty good job of explaining what we did in Gallery 3 and why:
http://gallery.menalto.com/gallery_3_begins
---
Problems? Check gallery3/var/logs
file a bug/feature ticket | upgrade to the latest code! | hacking G3? join us on IRC!