Hello,
I have a very large installation with K2 and a lot of pictures. The cache folder in the media folder is around 100.000 images large. I had some trouble with downloading all these pictures via FTP because most servers have a limit on the amount of items you can list. So I did some digging and found out a way to tackle this problem.
I have a comment regarding the image handling. Isn't it an idea to split up the image saving into folders with for example the year and the month (media/k2/items/src/2018/11/image.jpg , and , media/k2/items/cache/2018/11/image_S.jpg etc)
Because this way the server won't get slowed (Linux has a hard time with folders that are extremely large, filled with individual files) and you can access the files a lot easier with most configurations of the servers out there. I think also that K2 gets a speed boost if you go this route. Maybe something to think about?
Also I think it's an idea to built in a external server for spreading of the load of the website. For example use the Amazon S3 servers for your images. With a large website, images that gets pulled from the same server tend do dramatically slow the website down. A native solution where you directly upload the images to an external server would be nice.
Also regarding SIGPro, I really would like to have an option to use a external server to directly upload the images to, and also let the plugin directly generate the thumbnails (this gets done every 120 minutes standard). I think this could also drastically make the plugin more valuable and useful for websites with lots of images.
Is this something that is on the list of to do? Maybe I could help in getting this to work? I really like the K2 component and the Sigpro gallery plugin, but these 2 things are one of the most significant problems I encounter.
Thanks for reading.
I have a very large installation with K2 and a lot of pictures. The cache folder in the media folder is around 100.000 images large. I had some trouble with downloading all these pictures via FTP because most servers have a limit on the amount of items you can list. So I did some digging and found out a way to tackle this problem.
I have a comment regarding the image handling. Isn't it an idea to split up the image saving into folders with for example the year and the month (media/k2/items/src/2018/11/image.jpg , and , media/k2/items/cache/2018/11/image_S.jpg etc)
Because this way the server won't get slowed (Linux has a hard time with folders that are extremely large, filled with individual files) and you can access the files a lot easier with most configurations of the servers out there. I think also that K2 gets a speed boost if you go this route. Maybe something to think about?
Also I think it's an idea to built in a external server for spreading of the load of the website. For example use the Amazon S3 servers for your images. With a large website, images that gets pulled from the same server tend do dramatically slow the website down. A native solution where you directly upload the images to an external server would be nice.
Also regarding SIGPro, I really would like to have an option to use a external server to directly upload the images to, and also let the plugin directly generate the thumbnails (this gets done every 120 minutes standard). I think this could also drastically make the plugin more valuable and useful for websites with lots of images.
Is this something that is on the list of to do? Maybe I could help in getting this to work? I really like the K2 component and the Sigpro gallery plugin, but these 2 things are one of the most significant problems I encounter.
Thanks for reading.