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 know the file limitation is FTP related, but large folder with loads of files do hinder the perfomance of Linux: serverfault.com/questions/147731/do-large-folder-sizes-slow-down-io-performance It's better to distribute those files in subfolders, as I mentioned in my original post.

Ok, looking forward to the v4 of Sigpro.

As I read posts from out in the wild from other sites, this is one thing that always gets misunderstood about K2.
The way i see it K2 is a mousetrap that comes with the cheese! Keep up the good work, looking forward to the coming advances.

Hello,

I have a news portal with K2. The cache folder is the only thing that worries me in K2. I publish ~5-6 items per day (~2.000 per year). My cache folder has ~15.000 files but in a few years folder will have ~100.000 files or more. I worry about performance and hosting provider's reaction.

In my opinion, separating files in many folders (for example '/2018/12/' like in Wordpress) would be a good idea. Is it possible to implement this solution in the future releases of K2?

At the end, thank you for really great component. I am waiting for K2 Pro :)

Thank you for your reply :)

Hello,

If you are a developer, check out this plugin I made: github.com/afonic/rimage-k2

It offers much better image handling, multiple image sets, and it splits the generated images in folders for each item so it's nice and tidy.

Plus, you can now reorder galleries!

I'm not so much worried about the cache folder, more about the src folder which keeps a copy of all the original files uploaded. Since our authors don't really care about file size of the files they upload, with the knowledge K2 resizes all images in smaller sizes, they tend to upload huge files. Thus the src folder keeps growing in megabytes and takes a huge amount of my server storage. I need to clear this folder regularly via FTP, if I don't want to be billed by my hosting company for extra storage.