| < Previous by Date | Date Index | Next by Date > |
| < Previous in Thread | Thread Index | Next in Thread > |
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@xxxxxxxxxxxxxxx
List Archive: http://list.resiprocate.org/archive/resiprocate-users/