Live data from Hacker News

OpenRoss – fast, scalable, on-demand image resizer

developers.lyst.com

31–34 of 34 posts

Re: OpenRoss – fast, scalable, on-demand image resizer

#31
post #23

I'm curious to know how people feel about offline (pre-transformed) vs. on-demand transformations. Are there any HN'ers out there that have worked on a site with a large set of images, and have an opinion on this? Adobe's Scene7 product works in an offline mode as far as I can tell, and seems to have captured a large segment of retail companies with product catalogs.

I had worked for a social network, and our system provides a function to let user upload their photo then transform it to some fixed size of original one. We did have pre-transformed and on-demand too. Pre-transformed for the image that's most viewed by user, like new feed's photo (720x720), large photo (1024x768), and the origin one (if user's screen is detected as big screen), we have to resize it asap. Other sizes, like thumbnail, we do on-demand transform using nginx resize filter plugins, and caching using varnish and/or traffic server. That system have been working well until this time. I would say on-demand transformation is good idea, since you don't have to store resized-image that's never viewed by any user, so you save your storage. But that idea must be implemented well, very well if you're going to serve million users.

Re: OpenRoss – fast, scalable, on-demand image resizer

#32

There's also thumbor ( https://github.com/thumbor/thumbor ). It's a very mature implementation of this type of server and has been very battle-tested ( https://github.com/thumbor/thumbor/wiki/Who%27s-using-it ). At globo.com we have near a billion images (we are a big portal). Can you imagine pre-generating that many images every time a new format gets added? We serve everything with thumbor with a Varnish cache in f…

Is the amount of traffic the site gets worth billions of images?

Re: OpenRoss – fast, scalable, on-demand image resizer

#33

There's also thumbor ( https://github.com/thumbor/thumbor ). It's a very mature implementation of this type of server and has been very battle-tested ( https://github.com/thumbor/thumbor/wiki/Who%27s-using-it ). At globo.com we have near a billion images (we are a big portal). Can you imagine pre-generating that many images every time a new format gets added? We serve everything with thumbor with a Varnish cache in f…

Is the amount of traffic the site gets worth billions of images?

Definitely... We get around 50M page views/day in our website. And since we are a media company we need to have a storage of images from celebrities, sports and news in general.

Re: OpenRoss – fast, scalable, on-demand image resizer

#34
http://imageshack.us/pages/resize/ -- Our Imagizer cluster does 6 Gbps at the moment thats 750MBytes/sec all day long, its fast and scalable ;)

https://imageshack.com/discover All of the images here are rendered with Imagizer; We store all originals in our HBASE/Hadoop cluser, while Imagizer does on-demand tranformations.

It works with non-imageshack links too:

http://imagizer.imageshack.us/v2/500x500q90/http://actionfor...

Post reply on HN