Large AstDB – Millions Of Tuples – Issues?

Home » Asterisk Users » Large AstDB – Millions Of Tuples – Issues?
Asterisk Users 3 Comments

Hi all,
Does anyone uses astDB for a large amount of data, in special for implementing black lists with millions of numbers (i’d like about 2 or 3
million)?

That would be held in memory right? Is this (memory consumption) the only problem I could face?
Att. Gabriel

3 thoughts on - Large AstDB – Millions Of Tuples – Issues?

  • I have never tested something that large but I would think it would be slow. Why not use an age with reddis or mysql?

  • Hi Dovid,
    I’m trying to get rid of my AGIs. I wrote an * func to check directly my PG database, and then I saw that * already has a func_blacklist that will check astDB.
    I was thinking the issues I might have using astDB for it. If I do some performance tests I get back here with the results. Thanks, Gabriel

    2017-03-22 10:40 GMT-03:00 Dovid Bender :

  • We wrote a call screening (and CID rewrite) app for an ITSP a few years ago. We had to use MySQL as the astDB could not keep up (* was choking – we did dig deeper we just switched to MySQL). I don’t think astDB is the right way to go. If you’re comfortable writing a * func then you might as well go with MySQL.

    From: asterisk-users-bounces@lists.digium.com [mailto:asterisk-users-bounces@lists.digium.com] Hi all,

    Does anyone uses astDB for a large amount of data, in special for implementing black lists with millions of numbers (i’d like about 2 or 3 million)?

    That would be held in memory right? Is this (memory consumption) the only problem I could face?

    Att.

    Gabriel