Developer forum

Forum » CMS - Standard features » Image Handler taking too long

Image Handler taking too long

Nuno Aguiar Dynamicweb Employee
Nuno Aguiar
Reply

Hi,

 

We are noticing that the ImageHandler is taking too much time on the first image. Although we don't have a measured baseline, we woul expect it to be under 1,5sec.

The problem is that we're seeing it take more than 5 and even 10 seconds (even worse when the Product detail contains an image gallery and there are related products - the server gets hit with dozens of image requests concurrently). This is making the experience on the website unpleasant, and given the thousands of images VS the unique URL that can be generated through GetImage, we're always getting hit by the issue.

 

  • I am attaching an example image
  • A url generated by Swift templates looks like this /Admin/Public/GetImage.ashx?image=%2fFiles%2fImages%2fProducts%2f5043623002243%2f5043623002243_1.jpg&width=1920&format=webp
  • I tried it in jpg format, and although it's faster, it's still relatively slow
  • We started to notice this in 9.13.6 at least, and now in 9.13.11 the slowness persists. 
    (all with a standard installation of Dynamicweb - not changing the Image Provider)

 

Althouh the image has 2500 pixels in width and height, it's about 600Kb, meaning the expectation is that it should still process fast enough.

 

I know the right solution for such a project with lots of images is to use a CDN, but the post is in regards to a poor performance in general regarding the ImageHandler.

 

Can someone take a look and see if there's any performance issues with the default Image Provider.

 

Best Regards,

Nuno Aguiar

5043623002243_1.jpg

Replies

 
Nuno Aguiar Dynamicweb Employee
Nuno Aguiar
Reply

And maybe I posted a bit too soon (from my own threads http://doc.dynamicweb.com/forum/cms-standard-features/cms-standard-features/new-image-provider-whats-there-one).

 

We should probably start with changing to MagicScaler and see if there are still notable slowness, but if anyone knows and notices the same thing, we'd appreciate the answer

 
Adrian Ursu Dynamicweb Employee
Adrian Ursu
Reply

Hi Nuno,

We have seen something similar on one solution but in our case we have managed to solve it by adding an index on EcomDetails table for DetailProductID and DetailIsDefault.

Not sure if it will solve your issue but maybe it worth a try.

Adrian

 

 
Nuno Aguiar Dynamicweb Employee
Nuno Aguiar
Reply

Hi Adrian,

 

My test case can be proven requesting the image directly, so it's not related to any app. I just happened to mention Swift to provide some context as to how I got that URL, because using the backend Image Handler UI introduces more querystring parameters.

 

But thank you for chiming in and trying to help.

 

Nuno

 

You must be logged in to post in the forum