I notice the cpu load to be high even when there are few users.
Could you shed some light on how you prevented the Stack thread from hogging cpu.
Right now it keeps spinning and it only waits till its time to process the next stack message.
getTimeTillNextProcessMS()));
----- Original Message ----
From: Neil <neil.ban2008@xxxxxxxxx>
To: resiprocate-users@xxxxxxxxxxxxxxx
Sent: Thursday, January 31, 2008 4:24:20 AM
Subject: [reSIProcate-users] Resiprocate design
Hi,
I
had
a
question
regarding
the
design
of
Resiprocate.
We
are
using
the
resiprocate
stack
in
our
Server
product.
What
we
notice
is
that
in
load
scenarios
of
20000+
users,
the
cpu
usage
of
resiprocate
goes
up
very
significantly.
I
feel
the
Stackthread
to
be
the
bottleneck,
since
that
thread
is
doing
a
lot
of
operations
-
handling
transport(which
is
heavy
in
server
products),
sigcomp
processing(we
are
using
sigcomp)
and
transaction
layer
processing.
Do
you
think
it'l
be
a
good
idea
to
have
a
separate
transport
thread
to
do
the
transport
layers
operations,
and
let
the
stack
thread
do
the
sigcomp
and
other
stack
related
operations?
Thanks
_______________________________________________
resiprocate-users
mailing
list
resiprocate-users@xxxxxxxxxxxxxxxList
Archive:
http://list.resiprocate.org/archive/resiprocate-users/