It does cache images, controlled by the cache.config.

ok

do i need to add those settings to my web.config - configsettings?

i dont see this folder in my website - \config\imageprocessor\

Hi Mark

How did you install image processor? Have you followed the steps mentioned in "Getting started"? http://imageprocessor.org/getting-started.html

/Jan

I'm sorry, I always install ImageProcessor via NuGet, including the optional config package, but it's not a mandatory package.
The page states:

As of ImageProcessor.Web v3.2.0 configuration outwith the Web.Config file is not installed automatically. Instead default configuration matching the values below is built into the system.

I guess caching should be on by default. You said:

it seems to be processing on every page load where we use this, causing a delay in page rendering

How do you know? What did you do to conclude this? Any symptoms?

sorry for the confusion

i beleive it was an integral part of a recent umbraco upate, allowing us to resize images on the fly...

the pages with images are taking a significant longer time to load (10secsonds) as opposed to those without and server cpu jumps to 90% when rendering pages with images...

Hi Mark

Ah yes, indeed it is.

What exact version of Umbraco 7 are you using?

/Jan

7.1.7

Ok, yes then it's included out of the box. But as far as I can tell it's used for making crops when using the image cropper according to http://umbraco.com/follow-us/blog-archive/2014/3/20/release-candidates-of-umbraco-710-and-620-now-available

But it of course requires that you use and setup the image cropper http://our.umbraco.org/documentation/Using-Umbraco/Backoffice-Overview/Property-Editors/Built-in-Property-Editors-v7/Image-Cropper

If you are already using it like that then there might be a bug with it?

/Jan

ok possibly....

i cant see where any configuration is done within umbraco for this...

Hi Mark

If you have created the image cropper as a property editor and replaced it with the default upload property editor on an image item in the settings section then I don't think it should be necessary to do anything else.

But could you show some of the code you're using for rendering your images? And how large are they when you upload them?

/Jan

<img src="@Umbraco.TypedMedia(@child.GetPropertyValue("divisionSliderImage")).GetCropUrl(960, 300)"/>

but some are rendered by appending a querystring to the image and specifying the dimensions there...

Hi Mark.

Can you show us what the generated urls are like or even better link to a development server for me to look at.

It sounds to me like something is forcing ImageProcessor to reprocess the images on each visit which would mean the url is changing on each page load.

Could you also check for me what version of ImageProcessor and ImageProcessor.Web are installed?

You should be able to tell either by looking at the response headers for the images in the browser or in the bin folder for the site.

Cheers

James

is working on a reply...