Slow cache?

[simplenotezy]

I just installed the library. Hitting the route:

{route}/{template}/{filename}

Is extremely slow. It takes 500ms or so, compared to direct image source which is 20ms or so.

I wonder if the image is even cached. I suspect not. Using memcached as driver on a Laravel 5 installation.. How to debug further?

[simplenotezy]

On a page with 10-20 images, they take 10-15 seconds to load, and some of them even fail, like this:

[simplenotezy]

I've made a comparison:

Using imagecache:

Using direct image source:

[olivervogel]

I suggest to create a XDebug profile, to discover what is causing this delay.

[ghost]

canflax. Have the same problem, its faster to load image full size then cache'em. Please reply here if you find an answer! same for me

[DoubleTime]

Facing same issue, almost extra 60-70ms in time latancy.

This is the code how I load the image at Route.php

Route::get('images/cars/{src}', function ($src){    
    $cacheimage = Image::cache(function($image) use($src){
        return $image->make("images/products/".$src);
    },1440);

    return Response::make($cacheimage,200, array('Content-Type'=>'image/jpg'));
});

In blade

<img src="{{ URL::asset('/images/cars/theimage.jpg' }}" alt="">

Any thought? Using laravel 4 btw.

[mehrdd]

+1
is there any simple todo for real cache ?
i mean create a real thumbnail with Intervention's library.

[tshafer]

+1 I am also facing this issue. I am using it this way. http://image.intervention.io/use/url

[olivervogel]

I'm again suggesting to create a XDebug profile, to discover what exactly is causing this delay.

[tshafer]

Sorry about that.

Ill give it a try

[mosh-tudor]

Yep, getting pics from cache are so slow! Slow like first resizing.
http://c2n.me/3gUFhhr.jpg

[mosh-tudor]

NOTE!
Images from cache (I mean this script) have always HTTP status code 200,
in normal situation images must have HTTP status code 304.

I hope olivervogel will fix this!)

[jhellingman]

+1 Same issue with similar code.

[rogerfn]

People, any thoughts on it?

[Nikita240]

+1 same issue, even though it does create cached image files in the storage, and the Image::cache function is returning a CachedImage object.

[jhellingman]

The issue is that the entire framework needs to be loaded for each image being retrieved, and that action is actually slower than most image manipulations. Resolved by generating direct urls to generated images, and let the server pull them directly from the cache, without use of the framework. Since the types of manipulations I want are very limited, I can keep the URLs to them in my database and write them out to generated pages. My conclusion: I have no need for this framework.

[aske-cph]

+1 - Seems a tad useless for now.

Loading 8 images is very slow for me on a regular digital ocean droplet
It can sometimes take over 6 seconds to load a small group of images.

Sometimes the server hangs and loads all of the images at the same time. And i can see that the CPU spikes like crazy on the server, even though the images are cached.

I am going to just create a command in Laravel that creates the thumbs with intervention, and delegates the generated thumbs and different sizes to appropriate folders instead of relying on this for now...

[thanhmabo]

I also has same problem, see my cache image, actually slowly http://www.thanhmabo.com/post

[cmnstmntmn]

any update on this ?

[wi-development]

hello? always return 200, how to fix this?

[sunnyjayjay]

I agree. The caching is very much slower than loading the images directly. Is this problem going to be resolved or do we need to find another image caching solution?

[stephan-v]

Still slow as fuck, don't use this package.

[hijaumuda]

it's been 4 years, and still slow 👎

[theprobugmaker]

Have anyone found a solution or an alternative for this? @olivervogel