Yes no session is lost, and memory isn't wasted as with delta manager.
With 4 nodes,
when I ask 18080 or 28080 or 38080
node 48080 takes 2 more times than other two backup nodes,
now I stop all
now I tried starting nodes in order 2(8080),3,4,1 and started asking from 2
and not 4 was taking
in Manager app I see:
after
ab -k -n 100 -p post.txt http://localhost:18080/petclinic/session/fill
on 18080 in petclinic 100 sessions
on 28080 in petclinic 25 sessions
on 38080 in petclinic 25 sessions
on 48080 in petclinic 50 sessions yes two times more
after adding
ab -k -n 900 -p
On Tue, Feb 4, 2014 at 4:08 AM, Ja kub jjaku...@gmail.com wrote:
in Manager app I see:
after
ab -k -n 100 -p post.txt http://localhost:18080/petclinic/session/fill
on 18080 in petclinic 100 sessions
on 28080 in petclinic 25 sessions
on 38080 in petclinic 25 sessions
on 48080 in petclinic
On 02/02/2014 22:59, Ja kub wrote:
With below BackupManager backup manager configuration in server.xml
heap memory increases over 100MB on each of four nodes in cluster.
In addition time of
ab -c 10 -n 10 -p post.txt http://localhost:18080/petclinic/session/fill
is about 150 seconds
I have configured no loadbalancer,
I accessed tomcat directly
tomcats are on 18080, 28080, 38080, 48080,
In browser I used only 18080, this is my laptop test env, nobody else
access it,
28080, 38080, 48080, where untouched by broser, but in jvisualvm their
memory has increased by the same amount
On 03/02/2014 08:33, Ja kub wrote:
I have configured no loadbalancer,
I accessed tomcat directly
Both things that it would have been useful to mention in your original
question.
Before we go any further, how about telling us which Tomcat version you
are using?
Mark
tomcats are on 18080,
Good question, sorry I didn't tell earlier,
its tomcat 7.0.50 on linux, zip or tgz from download page, not from rpm.
On Mon, Feb 3, 2014 at 11:17 AM, Mark Thomas ma...@apache.org wrote:
On 03/02/2014 08:33, Ja kub wrote:
I have configured no loadbalancer,
I accessed tomcat directly
On 03/02/2014 11:03, Ja kub wrote:
Good question, sorry I didn't tell earlier,
its tomcat 7.0.50 on linux, zip or tgz from download page, not from rpm.
OK. Good to know it is the current release.
It is probably time to fire up a profiler and see where all the time is
being spent.
Mark
On
But time is not such a great problem for me. Time of execution was
mentioned only in addition - there are 100 k requests.
I am mainly interested in memory, and how BackupManager works.
I hoped, that with BackupManager memory will increase on node which is
queried and ONLY on one backup node,
but
On 03/02/2014 11:31, Ja kub wrote:
But time is not such a great problem for me. Time of execution was
mentioned only in addition - there are 100 k requests.
I am mainly interested in memory, and how BackupManager works.
I hoped, that with BackupManager memory will increase on node which is
Ok, thx,
2 questions:
1) If I will have only one very large session (about 100Mb), will memory
increase only on one backup node, and on 2 other nodes in cluster memory
will not increase ?
2) On 18080 node, on which all queries where asked memory increased not too
much than 100Mb, and on each of
On 03/02/2014 11:59, Ja kub wrote:
Ok, thx,
2 questions:
1) If I will have only one very large session (about 100Mb), will memory
increase only on one backup node, and on 2 other nodes in cluster memory
will not increase ?
You should see an increase on the primary and the backup node for
With below BackupManager backup manager configuration in server.xml
heap memory increases over 100MB on each of four nodes in cluster.
In addition time of
ab -c 10 -n 10 -p post.txt http://localhost:18080/petclinic/session/fill
is about 150 seconds
with default DeltaManager it is about 15
13 matches
Mail list logo
