21–30 of 48 posts
It seems unlikely that rack-cache + memcached would actually offer similar performance to varnish. This seems like a pretty bad set of changes for apps that need to serve out lots of static content - think newspapers, blogs, etc. Will the old configuration style for http caching continue to be supported indefinitely?
It seems unlikely that rack-cache + memcached would actually offer similar performance to varnish. This seems like a pretty bad set of changes for apps that need to serve out lots of static content - think newspapers, blogs, etc. Will the old configuration style for http caching continue to be supported indefinitely?
Oh, hey, it appears you can run python stuff too: https://gist.github.com/0a08e676559fc03e6200 kurt$ heroku run bash Running bash attached to terminal... up, run.2 ~ $ python -V Python 2.7.1 ~ $
Also Go and Erlang ~ $ go gobject-query godefs godoc gofix gofmt goinstall gomake gopack gopprof gotest gotry gotype govet goyacc ~ $ erl erl erlc
It seems unlikely that rack-cache + memcached would actually offer similar performance to varnish. This seems like a pretty bad set of changes for apps that need to serve out lots of static content - think newspapers, blogs, etc. Will the old configuration style for http caching continue to be supported indefinitely?
(Begs the question though: What are we doing serving pages >1MB?)
It seems unlikely that rack-cache + memcached would actually offer similar performance to varnish. This seems like a pretty bad set of changes for apps that need to serve out lots of static content - think newspapers, blogs, etc. Will the old configuration style for http caching continue to be supported indefinitely?
Where did you read about this new configuration?
"The new HTTP stack does not include Varnish (a reverse proxy cache) because it is not compatible with the advanced HTTP features described above. If you wish use HTTP caching headers, rack-cache and the memcache add-on offer features and performance comparable to Varnish, but with the additional benefit of giving you complete control over authentication and page expiration."
Earlier quoted context omitted.
Also Go and Erlang ~ $ go gobject-query godefs godoc gofix gofmt goinstall gomake gopack gopprof gotest gotry gotype govet goyacc ~ $ erl erl erlc
How do you output from bash/terminal to text like that?
"LXC used as a container for all dynos running on Celadon Cedar" Has anybody published a complete SELinux or SMACK policy to use LXC with untrusted users? Last I checked LXC wasn't fully ready yet.
Very interested to hear this as well. Anyone from Heroku can comment?
It seems unlikely that rack-cache + memcached would actually offer similar performance to varnish. This seems like a pretty bad set of changes for apps that need to serve out lots of static content - think newspapers, blogs, etc. Will the old configuration style for http caching continue to be supported indefinitely?
I love Varnish, but it's completely inflexible in Heroku so it's always been a mixed blessing. Sticking Google Analytics on your page, for instance, creates cookies for users that mean they will no longer get cached content. It's something that I can work around with dedicated Varnish, but Heroku can't really fix for me.
Oh, hey, it appears you can run python stuff too: https://gist.github.com/0a08e676559fc03e6200 kurt$ heroku run bash Running bash attached to terminal... up, run.2 ~ $ python -V Python 2.7.1 ~ $
Huh, so the Python support is pretty complete: Simple Flask app: https://gist.github.com/efec5e060e88abc87821 Python/Django: https://gist.github.com/866c79035a2d066a5850
"Run Anything
Run and scale any type of app."It seems unlikely that rack-cache + memcached would actually offer similar performance to varnish. This seems like a pretty bad set of changes for apps that need to serve out lots of static content - think newspapers, blogs, etc. Will the old configuration style for http caching continue to be supported indefinitely?
I expect that someone will build a Varnish add on for Heroku. It even looks possible to run Varnish on a dyno, believe it or not. I love Varnish, but it's completely inflexible in Heroku so it's always been a mixed blessing. Sticking Google Analytics on your page, for instance, creates cookies for users that mean they will no longer get cached content. It's something that I can work around with dedicated Varnish, but…
We've are running production apps with Varnish caching + Google Analytics without issue.
Set your cookies with JS or on uncached pages (such as POST logins) and you'll be fine.