1. You should configure JVM memory in nginx.conf, not in project.clj.
2. Nginx worker process JVM instance are in the same process but the
java heap memory is managed by JVM instance itself.
On Thursday, September 18, 2014 2:21:23 PM UTC+8, larry google groups wrote:
JVMs are not goot at
JVMs are not goot at huge memory management. Configurable multiple JVM
instances (is the
same number of Nginx Worker processes) will manage less memory. e.g. we
have ten
Nginx Worker processes in one Nginx instance every JVM instance will only
manage 1/10 memory
This is a stupid
Hi Yang,
'\0x09' is the same with '\t' , they get the same byte value 9. '\0x09'
and '\t' are just different human readable format display.
So for java *Wind ows NT*.equals(*Wind\tows NT*) .
By the way nginx-clojure won't do any converting about this case it just
keep the original value.
On 08/09/2014 04:20, Xfeep wrote:
In addition one Java thread will tie up one native OS thread.
A
On Monday, September 8, 2014 10:50:13 AM UTC+8, Yuexiang Zhang wrote:
Not only Wildfly but also most of mainstream pure java webservers
use thread pool to handle http requests.
0.2.5 (2014-09-07)
1. New Feature: Reference variables in jvm_options different jvm debug
ports for jvm processes (issue #42)
2. New Feature: Server Sent Events(SSE) Long polling (issue #41, issue
#36)
3. New Feature: Supports 64-bit JDK on 64-bit Windows (issue #40)
4.
On 07/09/2014 13:45, Yuexiang Zhang wrote:
0.2.5 (2014-09-07)
1. New Feature: Reference variables in jvm_options different jvm
debug ports for jvm processes (issue #42)
2. New Feature: Server Sent Events(SSE) Long polling (issue #41,
issue #36)
3. New Feature: Supports 64-bit
Sorry I don't use Immutant + Wildfly and know little about it.
The simple benchmarks including Immutant Nginx-Clojure can be found from
HERE https://github.com/ptaoussanis/clojure-web-server-benchmarks.
From Nginx-Clojure the most attractive things to us is :
1. Nginx's architecture is
On 07/09/2014 17:51, Yuexiang Zhang wrote:
From Nginx-Clojure the most attractive things to us is :
1. Nginx's architecture is Master + Worker processes, Nginx-Clojure
embed one JVM in per Worker process. So if any of worker process
crashes, the other JVM instances can still work and
Not only Wildfly but also most of mainstream pure java webservers use
thread pool to handle http requests. Nginx-Clojure can also be configurated
to use thread pool with one or many JVM instances.
Advanced Java webservers use Java NIO (I/O multipexing) to do the first
phrase (Http request
In addition one Java thread will tie up one native OS thread.
A
On Monday, September 8, 2014 10:50:13 AM UTC+8, Yuexiang Zhang wrote:
Not only Wildfly but also most of mainstream pure java webservers use
thread pool to handle http requests. Nginx-Clojure can also be configurated
to use
10 matches
Mail list logo
