Support Center

Recent questions

About Koken

This Help Center provides support for Koken, a free content management system designed for photographers, artists and designers.

Name is required.
Email address is required.
Invalid email address
Answer is required.
Exceeding max length of 5KB

Pre-Cache - It is really needed

Gene

Aug 27, 2014 12:08AM EDT

Your system's ability to generate images is really quite slow. I run very fast servers with dedicated RAM and CPU on a dedicated server account,, yet it still takes so long to generate new images that people are leaving thinking the images are broken. I know it is only Koken as my other sites with galleries produce their resized images at a fraction of the speed.

Would it be so hard to simply cache the images with a simple script?
All my WordPress websites have this ability. I can cache every page and image on the site with the press of a button.

This is particularly important for gallery sites like these.

Plus it's kinda of ridiculous for me to have to "view" all my uploaded images just to get them cached. It takes a long time to go through and "view" every image each time I upload a new gallery of images.

Up 0 rated Down

gene

Sep 05, 2014 02:54PM EDT
Wow ,, eight days and no response.. great support guys.
Up 0 rated Down

Team NetObjects Koken Agent

Sep 05, 2014 03:10PM EDT

Gene – We’ve noted your request for this in one of our many other responses to you, but just to put our position on this out in the open I’ll also add it here.

Image generation is a very touch subject for us to tackle. We create a wide variety of caches, so pre-caching them would take some time. Each image has a total of 7 presets. Each preset has a proportional and cropped version in both standard and retina formats. That means that each image could potentially create 28 separate caches. Pre-caching after an upload of 30 images, for example, could take a lot of time and some or many of those caches may never be used, so it would mean wasted space and CPU cycles. On top of that, 95% of our users are on shared hosts, and kicking off a CPU intensive process like that over a long period of time could potentially get them in hot water with their host, ending up in an account suspension. So if we just place an option to turn that on, people are going to click it without knowing about the consequences (because why wouldn’t you want to turn that on?).

So our focus in the near-term is improving the speed of the on-demand image processing as much as possible. We implemented improvements for ImageMagick in 0.17.4 that cut some rendering times in half. Also, we are putting together an guide for those on dedicated servers to help them get the most of the ImageMagick, Imagick or GraphicsMagick, as they can all be tuned a bit further to improve speed. I’ll update this thread when we have that article up.

We very well may attempt to address pre-caching in the future via a plugin or in the app itself, but it’s a complicated issue and would take some consideration and testing.

Let me know if you have any other questions.

Up 0 rated Down

gene

Sep 05, 2014 03:38PM EDT
Thank you,

I only keep harassing because it seems that throughout the forums (and the many people who have asked), Koken never "put our position on this out in the open". I wanted a straightforward statement like you've given....

If I can just get one more question answered, I'll stop asking about this:

The issue I simply cannot wrap my mind around is why Koken continues to worry about shared servers when it can be resolved with an on/off button in the settings. Everyone's happy that way.

Create the pre-cache script...
1) then for those on VPS or better we can simply turn it "on" if our servers allow for it.
It can even be done incrementally over time via a crone job thus allowing it to work even on shared servers.

I understand that for casual users just sharing photos of their dog, this is irrelevant,,, but Koken's goal, I thought, was to build a platform "made for photographers". For any professional photographer, most of our first time viewers are clients (or as important, prospective clients who will leave the website when they have to wait).

The best platform in the world is useless if visitors leave the site.
Up 0 rated Down

Team NetObjects Koken Agent

Sep 07, 2014 12:45AM EDT

> The issue I simply cannot wrap my mind around is why Koken continues to worry about shared servers when it can be resolved with an on/off button in the settings. Everyone’s happy that way.

If we provide a checkbox in Settings to enable a pre-cache, everyone would want to turn it on, no matter what server they have. Which could lead to problems.

Meanwhile, we’ve posted the article covering image processing I mentioned the other day. There is an advanced setup section at the bottom with tips on how to get the most out of your dedicated server.

Up 0 rated Down

gene

Sep 07, 2014 10:04AM EDT
1) add a warning message to it.
or
2) Make it something that we manually turn on in the code so only those comfortable with opening code (and therefore should know what kind of server they are on) can turn it on.
or
3) Make it an addon/plugin/or file download that people must go out of their way to implement. Again it can come with all the warnings.

and as I already mentioned, you could implement a crone job that spreads the process over time.

There is always a solution that helps everyone out.
Up 0 rated Down

Jerry Chen

Sep 14, 2014 01:32PM EDT
I might have a script that you needed/wanted.

https://jerry.im/essays/2014/06/pseudo-solution-to-generate-cache-images-for-koken/

This question has received the maximum number of answers.

support@koken.me
http://assets3.desk.com/
false
koken
Loading
seconds ago
a minute ago
minutes ago
an hour ago
hours ago
a day ago
days ago
about
false
Invalid characters found
/customer/en/portal/articles/autocomplete