Really? if I remember correctly, rails caching can work with a memory-store which is not shared between processes, or a drb/memcached store which is not a part of the process size.
But oh well, this isn't the rails list.
Daniel
ara.t.howard@noaa.gov wrote:
i wonder if people realize the size of a process is reported in virtual memory
and not in actual memory usage? in the case of something like rails tons of
the memory will be shared in the page cache.
it'd be great if you wanted to hack on acgi. my plans were to
- re-write using apache-apr so the c code would be platform independant
- support multiple backends. my plan was going to be to setup say 3
listeners and simply choose them at random when a request came in. this
should be very simply to code and scale linearly with the number of
servers.
the cool thing about acgi, of course, is that it's 100% web server independant
and doesn't even require special config. it's also totally transparent to the
rails app: which would merely switch FCGI -> ACGI. the simplicity means that
one could ftp upload a rails app to ANY server so long as it had cgi support
and a rails app would be fast. no config. no fastcgi. no mongrel. nothing
needed.
-a
On Sun, 4 Feb 2007, Daniel DeLorme wrote:
Ok, so from the answers so far I gather that something like this hasn't really been done before. Ara's acgi was quite similar to what I was hoping for, except without the concurrent connections.
I Guess I'll just have to scratch my own itch.
--
we can deny everything, except that we have the possibility of being better.
simply reflect on that.
- the dalai lama