Hi,
I installed 1.4.1.2 for a client, the gallery works good after pre-caching & static-html plug-in, but the admin is really slow.
The albums tab (10 albums) opens inner albums (after clicking any high level album) in about 10 seconds, but while saving (clicking the Apply button) it takes at least 30 seconds to get a response from the server.
I did search the forum about it, but found posts related to performance issues showing the gallery and none to admin.
The albums folder is composed by 3000 files in 300 directories
Any ideas to improve the performance?
Thanks
Comments
- Don't upload huge images dimensionwise (see troubleshooting)
- Set fixed album thumbs and not random (on the backend use the stand-in replacement album thumb)
One thing I have no clear is, what impact has the number of images in the whole gallery in the performance for a single album? I know the images inside have impact because of the thumb selection, but shouldn't be a scoped edit/save to the selected album?
Another thing I noticed (correct me if I'm wrong please), the whole albums' structure is processed while opening/selecting an album. Why I say that? because we have a problem with an album (mismatch filename & DB info) and the error message is appearing while selecting any album (high level or subalbums); although, this problem album is inside another main album
2. I am not sure I understand. If you open one album not the whole albums structure is processed. Without hte actual error message we really can'T answer to this specific problem. Of course the subalbum name (not title) includes the parent folder name
Example: The name of a subalbum "sublevel" to "toplevel" would be "toplevel/sublevel". So it is related.
Note also that 1.4.1.2 is not the latest version. My collegue who is more familiar with some of these internals liek form processing etc. will surely add some more details later.
In addition, the thumbnail displayed on the album tab may well be a different size from any on the front end, so will need to be created and cached the first time they are viewed.
There are all sorts of other possible reasons why a subalbum will be accessed when you are editing an album (for instance, you will notice there is a subalbum tab if and only if there are subalbums.)
As to the cause for your preformance issues, I do not have any ideas more than have been previously suggested.
my backend is very slow, it takes about 30 seconds to go into the album to save changes oder anything else whith has to do with the album or images.
i read this
"(on the backend use the stand-in replacement album thumb)"
but can't find it. please tell me where to find this setting.
Michael
Also it helps to only show one level at the time.
for me it doesn't help it takes very long to open a album.
but it would be better to set this as a gallery setting and not at each album i think. cause i was searching for at the settings and not at the albums. also i wouldn't have now to go to each subalbum and set this in hope that it would speed up the album backend at all.
Taking long to open an album probably is because of either using a random thumbnail or having the images shown in the thumbnail selector. You should first be sure the latter is reset.
Regarding the button: was there no button if the gallery was not in English? If so we have a translation issue we need to address.
i have no images shown in the thumbnailselector and for sure i want to have random thumbnails at the frontend only. i used the "show Thumbnail stand-in" button (is also shown in german).
my structure is album/sub/sub/images and album/sub/sub/sub/images too.
years ago you told me to insert in each album which has no image but subalbums inside a hidden pic to make it faster, but that didn't help too. i also changed several times the mysql server but this action didn't help too.
Important is also the size of the images and naturally the server speed.
Othewise, as acrylian has said. Make sure your images are of a size handleable by your server.
We really do not know why your server is slow. If it is just opening an album, then most likely the problem resides with the images in the album. But if that is image processing or SQL searching I really do not know.
Safari 4.1.x at least does also not show the thumbs in the selector, Firefox does.
sbilliard wrote: "But that does not mean that the image is not being generated."
so where is the sense for the option "show Thumbnail stand-in" than ?
my images are 640x480 which i upload and the size is between 50 and 100 kb so it is small enough i think.
i'm using ie and ff and it was in each version the same.
Btw, to avoid this on the front end the html static cache plugin exists.
You can disable the random thumbs itself on the option and on each album edit page individually.
sbilliard wrote: "...But that does not mean that the image is not being generated. ..."
Anyway, the main slowdown is if these thumb display needs to be generated and that for many albums wat once. The more image the bigger the chance it has not been already created (=cached). If then the images dimension wise are quite big and the server has problems to handle this adds up the more it needs to create.
Thus the standin image to avoid this on the backend.
We have no plans to change the thumb substitute behavior. First, it is unlikely it is your problem. Second, it is a one-time action. If you just make the settings rather than complain you will have spent less effort.