Dear All, I use nibllebill + postgresql for longtime. it' work wel when concurrent about 500 calls.. Now i have 1200 calls . postgresql got many problem and slow. so i have 2 choice. 1. upgrade hardware , add more memory may be 32 GB and change HDD to SSD (or IOdrive ). 2. split DB some path to NoSQL (I'm testing memcachedb,redis,tokyo tyrant) I choose 2. and use tokyo tyrant. because it's persistant and support memcache API. Today i create new module base on nibblebill but use memcacahe API connect to tokyo tyrant. it's look fast. and work without any problem. If someone want to use my module I'l acttach to JIRA and create WIKI page. Please let's me know if you want. BG Dome C.
Hi Dome, postgresql is a very powerful DB that can accepts a lot of simultaneous connections it needs to be set carefully to fit your memory and HD. try google postgresql tuning However the other solution can be interesting too. Regards F ----- Original Message ----- From: "Dome Charoenyost" <dome@tel.co.th> To: <freeswitch-users@lists.freeswitch.org> Sent: Wednesday, March 03, 2010 1:38 AM Subject: [Freeswitch-users] Nibblebill for NoSQL
Dear All, I use nibllebill + postgresql for longtime. it' work wel when concurrent about 500 calls.. Now i have 1200 calls . postgresql got many problem and slow. so i have 2 choice. 1. upgrade hardware , add more memory may be 32 GB and change HDD to SSD (or IOdrive ). 2. split DB some path to NoSQL (I'm testing memcachedb,redis,tokyo tyrant) I choose 2. and use tokyo tyrant. because it's persistant and support memcache API. Today i create new module base on nibblebill but use memcacahe API connect to tokyo tyrant. it's look fast. and work without any problem. If someone want to use my module I'l acttach to JIRA and create WIKI page.
Please let's me know if you want.
BG Dome C.
_______________________________________________ FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
Dome I am very interested in your module. Please add it to JIRA and create a WIKI page for it. And does everything else that used to be on your postgresql now being migrated to the memcache API + tokyo tyrant? On Wed, Mar 3, 2010 at 2:38 PM, Dome Charoenyost <dome@tel.co.th> wrote:
Dear All, I use nibllebill + postgresql for longtime. it' work wel when concurrent about 500 calls.. Now i have 1200 calls . postgresql got many problem and slow. so i have 2 choice. 1. upgrade hardware , add more memory may be 32 GB and change HDD to SSD (or IOdrive ). 2. split DB some path to NoSQL (I'm testing memcachedb,redis,tokyo tyrant) I choose 2. and use tokyo tyrant. because it's persistant and support memcache API. Today i create new module base on nibblebill but use memcacahe API connect to tokyo tyrant. it's look fast. and work without any problem. If someone want to use my module I'l acttach to JIRA and create WIKI page.
Please let's me know if you want.
BG Dome C.
_______________________________________________ FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
-- Henry Huang UniC Solution - Communication Unified VoIP & Open Source software Consultant
im VERY interested in this... ( and the use of NoSQL in general with FS ) please can you email over what you have, or post it to jira. J On Wed, Mar 3, 2010 at 4:38 PM, Dome Charoenyost <dome@tel.co.th> wrote:
Dear All, I use nibllebill + postgresql for longtime. it' work wel when concurrent about 500 calls.. Now i have 1200 calls . postgresql got many problem and slow. so i have 2 choice. 1. upgrade hardware , add more memory may be 32 GB and change HDD to SSD (or IOdrive ). 2. split DB some path to NoSQL (I'm testing memcachedb,redis,tokyo tyrant) I choose 2. and use tokyo tyrant. because it's persistant and support memcache API. Today i create new module base on nibblebill but use memcacahe API connect to tokyo tyrant. it's look fast. and work without any problem. If someone want to use my module I'l acttach to JIRA and create WIKI page.
Please let's me know if you want.
BG Dome C.
_______________________________________________ FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
-- Sincerely Jay
Hi.. I'm interesting too.. Thanks :) On Wed, Mar 3, 2010 at 3:42 AM, jay binks <jaybinks@gmail.com> wrote:
im VERY interested in this... ( and the use of NoSQL in general with FS )
please can you email over what you have, or post it to jira.
J
On Wed, Mar 3, 2010 at 4:38 PM, Dome Charoenyost <dome@tel.co.th> wrote:
Dear All, I use nibllebill + postgresql for longtime. it' work wel when concurrent about 500 calls.. Now i have 1200 calls . postgresql got many problem and slow. so i have 2 choice. 1. upgrade hardware , add more memory may be 32 GB and change HDD to SSD (or IOdrive ). 2. split DB some path to NoSQL (I'm testing memcachedb,redis,tokyo tyrant) I choose 2. and use tokyo tyrant. because it's persistant and support memcache API. Today i create new module base on nibblebill but use memcacahe API connect to tokyo tyrant. it's look fast. and work without any problem. If someone want to use my module I'l acttach to JIRA and create WIKI page.
Please let's me know if you want.
BG Dome C.
_______________________________________________ FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
-- Sincerely
Jay
_______________________________________________ FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
On 03/03/2010 12:38 AM, Dome Charoenyost wrote: <snip snip>
Today i create new module base on nibblebill but use memcacahe API connect to tokyo tyrant. it's look fast. and work without any problem. If someone want to use my module I'l acttach to JIRA and create WIKI page.
Please let's me know if you want.
BG Dome C.
Maybe it would be even more useful to provide general functionality that can be shared amongst multiple components of freeswitch. That would make it all the more useful. However, seeing that I'm not a big fan of the NoSQL data engines, I don't know if this is possible. In my opinion, most NoSQL is just key=>value pairs, and is basically a reinvention of the wheel that RDBMS's had taken care of years ago... Not meaning to open up a discussion about the virtues of NoSQL (and certainly not a flamewar)... Yossi Neiman Cartis Solutions, Inc. - http://www.cartissolutions.com
On Wed, Mar 3, 2010 at 12:04 PM, Yossi Neiman < freeswitch@cartissolutions.com> wrote:
Maybe it would be even more useful to provide general functionality that can be shared amongst multiple components of freeswitch. That would make it all the more useful. However, seeing that I'm not a big fan of the NoSQL data engines, I don't know if this is possible. In my opinion, most NoSQL is just key=>value pairs, and is basically a reinvention of the wheel that RDBMS's had taken care of years ago... Not meaning to open up a discussion about the virtues of NoSQL (and certainly not a flamewar)...
I created a mod_memcache already and I intend to do a mod_redis at some point. I'm not a huge fan of NoSQL but there are definite uses for it. General functionality: I could be convinced to come up with a general api for distributed key/value store with mod_memcache and mod_redis providing implementation. The problem is that the NoSQL stuff isn't very consistent so even though both support key/value their behavior can significantly differ. eg: updating a value in memcached doesn't bump the expire time but does in redis. Also, redis has support for a much more robust set of value types and operators. Anyway, a generic distributed key/value api might look like: dhash <backend> set key value [expire] dhash <backend> setnx key value [expire] # only set if it doesn't already exist dhash <backend> get key [...] # support multiple keys dhash <backend> <increment|decrement> key [step] dhash <backend> del key where backend would be memcache or redis or some other implementation. Notice I didn't even touch things like hashing to support sharding, failover, etc.
Yossi Neiman Cartis Solutions, Inc. - http://www.cartissolutions.com
-- -Rupa
Hi Rupa, any update about NoSQL module. Now i'm modify mod_limit change sql to tokyo tyrant. it's work fine for me. now i can share limit data to other FS server. Now i'm thinking about all fs db. if use redis (sorted sets) i think posible todo. but it's not easy to modify fs code. So i need comment about aventage if change fs backend froom SQL to NoSQL. BG Dome C. 2010/3/4 Rupa Schomaker <rupa@rupa.com>:
On Wed, Mar 3, 2010 at 12:04 PM, Yossi Neiman <freeswitch@cartissolutions.com> wrote:
Maybe it would be even more useful to provide general functionality that can be shared amongst multiple components of freeswitch. That would make it all the more useful. However, seeing that I'm not a big fan of the NoSQL data engines, I don't know if this is possible. In my opinion, most NoSQL is just key=>value pairs, and is basically a reinvention of the wheel that RDBMS's had taken care of years ago... Not meaning to open up a discussion about the virtues of NoSQL (and certainly not a flamewar)...
I created a mod_memcache already and I intend to do a mod_redis at some point. I'm not a huge fan of NoSQL but there are definite uses for it.
General functionality: I could be convinced to come up with a general api for distributed key/value store with mod_memcache and mod_redis providing implementation. The problem is that the NoSQL stuff isn't very consistent so even though both support key/value their behavior can significantly differ. eg: updating a value in memcached doesn't bump the expire time but does in redis. Also, redis has support for a much more robust set of value types and operators. Anyway, a generic distributed key/value api might look like: dhash <backend> set key value [expire] dhash <backend> setnx key value [expire] # only set if it doesn't already exist dhash <backend> get key [...] # support multiple keys dhash <backend> <increment|decrement> key [step] dhash <backend> del key where backend would be memcache or redis or some other implementation. Notice I didn't even touch things like hashing to support sharding, failover, etc.
Yossi Neiman Cartis Solutions, Inc. - http://www.cartissolutions.com
-- -Rupa
_______________________________________________ FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
I have mod_redis ready, it'll go in soon. Mathieu Rene Avant-Garde Solutions Inc Office: + 1 (514) 664-1044 x100 Cell: +1 (514) 664-1044 x200 mrene@avgs.ca On 2010-04-22, at 2:03 PM, Dome Charoenyost wrote:
Hi Rupa,
any update about NoSQL module. Now i'm modify mod_limit change sql to tokyo tyrant. it's work fine for me. now i can share limit data to other FS server. Now i'm thinking about all fs db. if use redis (sorted sets) i think posible todo. but it's not easy to modify fs code.
So i need comment about aventage if change fs backend froom SQL to NoSQL.
BG
Dome C.
2010/3/4 Rupa Schomaker <rupa@rupa.com>:
On Wed, Mar 3, 2010 at 12:04 PM, Yossi Neiman <freeswitch@cartissolutions.com> wrote:
Maybe it would be even more useful to provide general functionality that can be shared amongst multiple components of freeswitch. That would make it all the more useful. However, seeing that I'm not a big fan of the NoSQL data engines, I don't know if this is possible. In my opinion, most NoSQL is just key=>value pairs, and is basically a reinvention of the wheel that RDBMS's had taken care of years ago... Not meaning to open up a discussion about the virtues of NoSQL (and certainly not a flamewar)...
I created a mod_memcache already and I intend to do a mod_redis at some point. I'm not a huge fan of NoSQL but there are definite uses for it.
General functionality: I could be convinced to come up with a general api for distributed key/value store with mod_memcache and mod_redis providing implementation. The problem is that the NoSQL stuff isn't very consistent so even though both support key/value their behavior can significantly differ. eg: updating a value in memcached doesn't bump the expire time but does in redis. Also, redis has support for a much more robust set of value types and operators. Anyway, a generic distributed key/value api might look like: dhash <backend> set key value [expire] dhash <backend> setnx key value [expire] # only set if it doesn't already exist dhash <backend> get key [...] # support multiple keys dhash <backend> <increment|decrement> key [step] dhash <backend> del key where backend would be memcache or redis or some other implementation. Notice I didn't even touch things like hashing to support sharding, failover, etc.
Yossi Neiman Cartis Solutions, Inc. - http://www.cartissolutions.com
-- -Rupa
_______________________________________________ FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
_______________________________________________ FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
2010/4/23 Mathieu Rene <mrene_lists@avgs.ca>:
I have mod_redis ready, it'll go in soon.
very good news. Dome C.
Mathieu Rene Avant-Garde Solutions Inc Office: + 1 (514) 664-1044 x100 Cell: +1 (514) 664-1044 x200 mrene@avgs.ca
On 2010-04-22, at 2:03 PM, Dome Charoenyost wrote:
Hi Rupa,
any update about NoSQL module. Now i'm modify mod_limit change sql to tokyo tyrant. it's work fine for me. now i can share limit data to other FS server. Now i'm thinking about all fs db. if use redis (sorted sets) i think posible todo. but it's not easy to modify fs code.
So i need comment about aventage if change fs backend froom SQL to NoSQL.
BG
Dome C.
2010/3/4 Rupa Schomaker <rupa@rupa.com>:
On Wed, Mar 3, 2010 at 12:04 PM, Yossi Neiman <freeswitch@cartissolutions.com> wrote:
Maybe it would be even more useful to provide general functionality that can be shared amongst multiple components of freeswitch. That would make it all the more useful. However, seeing that I'm not a big fan of the NoSQL data engines, I don't know if this is possible. In my opinion, most NoSQL is just key=>value pairs, and is basically a reinvention of the wheel that RDBMS's had taken care of years ago... Not meaning to open up a discussion about the virtues of NoSQL (and certainly not a flamewar)...
I created a mod_memcache already and I intend to do a mod_redis at some point. I'm not a huge fan of NoSQL but there are definite uses for it.
General functionality: I could be convinced to come up with a general api for distributed key/value store with mod_memcache and mod_redis providing implementation. The problem is that the NoSQL stuff isn't very consistent so even though both support key/value their behavior can significantly differ. eg: updating a value in memcached doesn't bump the expire time but does in redis. Also, redis has support for a much more robust set of value types and operators. Anyway, a generic distributed key/value api might look like: dhash <backend> set key value [expire] dhash <backend> setnx key value [expire] # only set if it doesn't already exist dhash <backend> get key [...] # support multiple keys dhash <backend> <increment|decrement> key [step] dhash <backend> del key where backend would be memcache or redis or some other implementation. Notice I didn't even touch things like hashing to support sharding, failover, etc.
Yossi Neiman Cartis Solutions, Inc. - http://www.cartissolutions.com
-- -Rupa
_______________________________________________ FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
_______________________________________________ FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
_______________________________________________ FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
Dome, I personally don't have any plans to add NoSQL to nibblebill. If you have a patch or a bounty maybe that could change, But for now, SQL works for me. On Thu, Apr 22, 2010 at 1:03 PM, Dome Charoenyost <dome@tel.co.th> wrote:
Hi Rupa,
any update about NoSQL module. Now i'm modify mod_limit change sql to tokyo tyrant. it's work fine for me. now i can share limit data to other FS server. Now i'm thinking about all fs db. if use redis (sorted sets) i think posible todo. but it's not easy to modify fs code.
So i need comment about aventage if change fs backend froom SQL to NoSQL.
BG
Dome C.
2010/3/4 Rupa Schomaker <rupa@rupa.com>:
On Wed, Mar 3, 2010 at 12:04 PM, Yossi Neiman <freeswitch@cartissolutions.com> wrote:
Maybe it would be even more useful to provide general functionality that can be shared amongst multiple components of freeswitch. That would make it all the more useful. However, seeing that I'm not a big fan of the NoSQL data engines, I don't know if this is possible. In my opinion, most NoSQL is just key=>value pairs, and is basically a reinvention of the wheel that RDBMS's had taken care of years ago... Not meaning to open up a discussion about the virtues of NoSQL (and certainly not a flamewar)...
I created a mod_memcache already and I intend to do a mod_redis at some point. I'm not a huge fan of NoSQL but there are definite uses for it.
General functionality: I could be convinced to come up with a general api for distributed key/value store with mod_memcache and mod_redis providing implementation. The problem is that the NoSQL stuff isn't very consistent so even though both support key/value their behavior can significantly differ. eg: updating a value in memcached doesn't bump the expire time but does in redis. Also, redis has support for a much more robust set of value types and operators. Anyway, a generic distributed key/value api might look like: dhash <backend> set key value [expire] dhash <backend> setnx key value [expire] # only set if it doesn't already exist dhash <backend> get key [...] # support multiple keys dhash <backend> <increment|decrement> key [step] dhash <backend> del key where backend would be memcache or redis or some other implementation. Notice I didn't even touch things like hashing to support sharding, failover, etc.
Yossi Neiman Cartis Solutions, Inc. - http://www.cartissolutions.com
-- -Rupa
_______________________________________________ FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
_______________________________________________ FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
-- -Rupa
On Thu, Apr 22, 2010 at 2:53 PM, Rupa Schomaker <rupa@rupa.com> wrote:
Dome,
I personally don't have any plans to add NoSQL to nibblebill. If you have a patch or a bounty maybe that could change, But for now, SQL works for me.
Is there any valid reason to go nosql-ish for nibblebill? -MC
participants (9)
-
Dome Charoenyost
-
Henry Huang
-
Javier Aristizábal
-
jay binks
-
Madovsky
-
Mathieu Rene
-
Michael Collins
-
Rupa Schomaker
-
Yossi Neiman