it seems like the only difference would be 4 garbage collectors working on
smaller heaps, however there would be much more memory overhead that way.
I assume if you can load-balance your app like that, that it is stateless,
and won't use a whole bunch of static memory. You might do better wit
Thank you both..
This information was really helpful.
Tim
On Oct 20, 6:05 pm, Andy Fingerhut wrote:
> I would suspect that you would not get a _significant_ performance advantage
> from specifying processor affinity, but if you really want to measure it and
> find out by experimentation, read on.
I would suspect that you would not get a _significant_ performance advantage
from specifying processor affinity, but if you really want to measure it and
find out by experimentation, read on.
I was not able to find any portable way within a JVM to set processor
affinity, after some amount of Googl
I don't think so. Jetty is also multi-threaded; each request will be served
by a new thread (within a bounded thread pool). Secondly, processor
affinity is almost always a bad idea; the OS is pretty good at doing this
for you.
At the very least I would have a test harness which measures the beha
This may not be a Clojure specific kind of question, but this is for
my Clojure web app(s) so hopefully it's not too far off.
Currently when I deploy my web apps I run 1 app instance on 1 app
server. Given these are multi-core servers I am thinking about running
4 app instances on a server to get
