On Thu, 25 Oct 2012 17:47:45 -0200, George Christman
<gchrist...@cardaddy.com> wrote:
We seem to be pushing our processor limits while
processing photo's at peak times of the day, so I was looking for an
affordable way to scale the processors at those times of the day.
Why, at least for now, don't you use AWS or a VPS just for the image
processing and leave the rest as it is now? That seems to be your
bottleneck now. Usually, the web app itself isn't the bottleneck, but the
database or in some external processing like you do in your images.
The majority of our user base is outside of our local area, so I was
hoping for some sort of CDN, however I'm not sure how tapestry uses this
though.
Just generate <img> elements with src attributes pointing to wherever the
images are stored.
--
Thiago H. de Paula Figueiredo
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
