On 22.09.2020 18:42, Ovidiu Sas wrote:
If you don't want to run a full blown db, then you can use db_text
without cacheDB.
The data is cached into memory at startup. If you update the text
file, you can re-cache the data [1].
Hi, Ovidiu!
May I segue into discussing some questions that have bee
I personally like memcached because of it's speed and the availability of
SDKs to work with it in so many languages. These are all good choices tho!
I think the quantity and how frequently your data changes is a big factor.
If you have a lot of data that tends to change, I'd use memcache. If it's a
Hello Alain,
If you don't want to run a full blown db, then you can use db_text
without cacheDB.
The data is cached into memory at startup. If you update the text
file, you can re-cache the data [1].
You can also manipulate the data using the avpops module [2].
Or, you can use cacheDB on top of th
SIP UDP Interface #1 (udp:10.169.115.19:5073)
Receive Queue: 4.8KB
Avg. CPU usage: 0% (last 1 sec)
Process 6 load: 12%, 10%, 3% (SIP receiver udp:10.169.115.19:5073)
Process 7 load: 13%, 10%, 4% (SIP receiver udp:10.169.115.19:5073)
Process 8 load: 13%, 10%, 4% (SIP recei
Memcache is a great fit for this. Load the data in externally or thru
programmatic cache_miss. This method supports a very high rate per second.
Just be sure to consider failure cases. Caches should never be expected to
be right 100% of the time. They need to be expected and allowed to fail
gracefu
On 22.09.2020 16:09, Alain Bieuzent wrote:
I need to store some data locally but accessible by opensips.
the data is almost 20 records made up of a couple IP: name
From opensips script I want to retrieve the name associated with the
IP (to put in place profiling).
how do you set up this kin
Hi all,
I need to store some data locally but accessible by opensips.
the data is almost 20 records made up of a couple IP: name
>From opensips script I want to retrieve the name associated with the IP (to
>put in place profiling).
how do you set up this kind of solution without acces
