Hi Will

This is in relation to the image storage issue.  

I found this app that I intend using for our site.   It basically allows you to upload one file and then it automatically will reduce file size wherever and whenever you want.   And it does all this on the fly.

For example, you can have the same image appear in different places in different sizes and the server creates those images on the fly from the larger image.

This eliminates the need to store several sizes of the same image.   As far as I can tell the served images are discarded after being served.

Is there any way we can incorporate this app into AS so we can cut down on file storage?


http://nathanaeljones.com/products/...e-resizer/

Thanks

When architecting systems you have to balance many resources.

Your concern is around disk space, but implementing the solution you suggest increases both processing and memory usage when the image is served. Also, if you want to maintain the quality of the largest size, then you have to store that image. Usually the smaller ones are an order of magnitude smaller than that large image.

Depending on the application, that might make sense. In most of our applications, I tend to see that photo uploaded one time and served many times. I would rather take the processing hit up front once than multiple times when served.

Also if you look at a pure cost / benefit perspective, increasing disk space tends to be much cheaper than increasing either processing power or memory.

Just my 2 cents

Exactly what Raymond said.

It's a good idea and would be well suited for a personal blog. For something that is going to display 20-30 thumbnails on page viewed by many users at a time this solution would peg your processors. Yes, our current method has the potential for using more disk space, but disk space is cheaper than processor cycles.

Fair enough. Good points.

Hi, sorry for bumping an old thread - but in defense of my product, the disk caching eliminates the higher CPU usage concerns you were worried about.

Since the images are cached to disk, all the serving of the images can be done by IIS, not the module, which eliminates the overhead.

You can also control how much space you want to dedicate to the disk cache, so you don't have to sacrifice EITHER of the two - you can keep both CPU and disk usage very low.

I know several DotNetNuke websites that are using the ImageResizer right now with no issues. No user of this product (as far as I know) has ever encountered performance or scalability issues that weren't easily resolved by fixing their configuration error.

It's used on catalog sites that host (and resize) 500,000+ images, and has been integrated into dozens of CMSes. Thousands of web sites use it.

And I've never had a dissatisfied user in the past 4 years. Every support ticket has been resolved.

If you have any non-theoretical issues with the product, please e-mail me at support@imageresizing.net and I'll be happy to resolve them.

By the way - the entire product is open-source (the core and all plugins). The core and 9 plugins are free, the other plugins have a 'download fee' that pays for support and development.

I've been very careful from the beginning to make sure the licenses were compatibile with open-source projects such as DotNetNuke so that they could be integrated and redistributed.