30 May
2005
30 May
'05
12:41 a.m.
At 03:15 PM 5/29/2005, Java Rockx wrote:
Actually, a minute delay would be a bad thing because
replicated usrloc records, using t_replicate() would not make it in to peer SER server
caches when the server is starting up.
Given this fact, and given the fact that most SER modules do not hash data upon server
startup [like group.so, etc, etc] we are starting to see little value in caching usrloc.
Our MySQL server is hit 12 times for an INVITE message and so complete caching of usrloc
is of minimal performace gain.
indeed.
Anyhow, we're not in process of modifying SER so
that:
* when ser starts up usrloc is "lazy-loaded"
* if a usrloc record is looked up in cache and is __NOT__ found, then MySQL will be
queried. If found in MySQL then the usrloc record will be put in to cache for future
lookups
By doing these two things we should not have a problem we excessively large subscriber
bases.
Appears reasonable to me.
Still -- with the way you are suggesting, CallID based load distribution, how
do you replicate UsrLoc changes across all the servers?
-jiri