This is all unnecessary, just toss them on tmpfs and call it a day. Mike On Feb 16, 2010, at 6:04 PM, Paulo Vicentini wrote:
Hello, "The core will open the db multiple times so you would end up with many instances not linked to each other."
I think it might work with just one core.db handle, right?
"If sofia uses it, it needs it, or else it would've been an optional configuration option."
As I can see until now, if mod_sofia were used just as a gateway (that is my aim) it would be able to bypass sip related tables/code and it might have a compile option for that scenario as well...
"How hard are you hitting this box to kill it because your data base ? What distro are you on?" I intend to use my hacked FS version on Debian / Kernel 2.6.23.8 / soekris
Thank you, Paulo
On Mon, Feb 15, 2010 at 7:45 PM, Brian West <brian@freeswitch.org> wrote: How hard are you hitting this box to kill it because your data base ? What distro are you on? Some versions of the linux kernel slow SQLITE down by 400-1000% depending on the kernel rev.
/b
On Feb 15, 2010, at 3:41 PM, Paulo Vicentini wrote:
I will try to enable such feature in core.db ( I want to use just RAM core.db and to disable all other databases) If I use FS exclusively as a SIP gateway ( no registrar ) I think I can "disable" the use of such sofia tables (Does it make sense? ) :
.tables sip_authentication sip_shared_appearance_dialogs sip_dialogs sip_shared_appearance_subscriptions sip_presence sip_subscriptions sip_registrations
Thank you Paulo