You can make a load test and get that number. For example at my sipp test, I got about 15xM RAM when cps is 200 and concurrent call 1200. So if I think my app's maximum call limit is that value, I will set it into 180M. regards Gang On Mon, Jan 19, 2009 at 9:29 PM, Mark Webster <mark.webster+pjsip at gmail.com<mark.webster%2Bpjsip at gmail.com> > wrote: > I'm going to do a little "dance of stupid" here now, for your > entertainment. > > For some reason, I thought that passing a limit of "0" to > pj_caching_pool_init() would cause it to have no limit (ie, always use > cache). Looking at the docs and code, obviously that was a bit silly! > > I guess my problem now is guessing intelligently what the limit should be, > considering I have multiple installations dealing with different loads. I > suppose if I just pass a REAL_BIG_NUMBER, it should be safe? > > I'm going to test this live tomorrow. I'm sure it will solve the problem. > Thanks for your help! > > -Mark > > On Mon, Jan 19, 2009 at 12:27 PM, Benny Prijono <bennylp at teluu.com> wrote: > >> On Mon, Jan 19, 2009 at 12:06 PM, Mark Webster < >> mark.webster+pjsip at gmail.com <mark.webster%2Bpjsip at gmail.com>> wrote: >> >>> Yeah, I was pretty sure that's what the caching pool does. I'm going to >>> have to go through the code carefully to find out why my silly pool caching >>> algorithm seems to "hide" the problem. I've been running it live for a while >>> now and the memory usage seems very stable, compared to last week when I >>> experienced this crash the first time. >>> >>> Anyway I'll take your advice and try to get to the bottom of this. I'll >>> get back to the list with my findings later in the week. >>> >>> >> A bit more info from me. Gang Liu and I discussed this few months back >> here: >> http://lists.pjsip.org/pipermail/pjsip_lists.pjsip.org/2008-September/004728.html >> >> In the end, we concluded that it was LIBC that does the caching and not >> PJLIB, so this may also be the case yours. If so, then perhaps it'll be more >> appropriate to let PJLIB's caching pool to do the caching by setting it's >> cache value to some high number. >> >> Cheers >> Benny >> >> >> >> >> _______________________________________________ >> Visit our blog: http://blog.pjsip.org >> >> pjsip mailing list >> pjsip at lists.pjsip.org >> http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org >> >> > > _______________________________________________ > Visit our blog: http://blog.pjsip.org > > pjsip mailing list > pjsip at lists.pjsip.org > http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org > > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.pjsip.org/pipermail/pjsip_lists.pjsip.org/attachments/20090119/30a92ae5/attachment.html>
