Let me start by thanking anyone for sharing his views. Definitely, as I mentioned, low traffic has different requirements than heavier. In the design document that I am preparing, I include sizing and capacity planning along with recommendations for each level. Based on this analysis, the client can decide the system for him. As Alejandro put it, it might just boil down to simple preferences or know-how.
BR, Nikos ----- Original--Message ----- From: [email protected] To: 'Nikos Balkanas' ; 'Alejandro Guerrieri' Cc: [email protected] Sent: Thursday, January 22, 2009 7:24 PM Subject: RE: DLR DB processing Nikos, It seems that the database will have only one dedicated task. If your concerns relate to the load, speed or locking specific of the database, good solution could be to determine the average amount of data transmitted on the unit of time and target volume. Clarification of customer requirements can help in making the right choice. Regards, Jarek ------------------------------------------------------------------------------ From: Nikos Balkanas [mailto:[email protected]] Sent: Thursday, January 22, 2009 5:01 PM To: Alejandro Guerrieri Cc: Jarek Guzik; [email protected] Subject: Re: DLR DB processing Actually no, I mean SQLBox v. 1.3 as in http://www.doldersum.com/sqlbox/sbox_archives.html. Bless me, though! It is not even supported in Kannel. Another good reason to scratch this one out.;-) BR, Nikos ----- Original Message ----- From: Alejandro Guerrieri To: Nikos Balkanas Cc: Jarek Guzik ; [email protected] Sent: Thursday, January 22, 2009 4:39 PM Subject: Re: DLR DB processing With SQLBox you mean MS SQL Server I guess? ;) Regards, Alex On Thu, Jan 22, 2009 at 3:30 PM, Nikos Balkanas <[email protected]> wrote: Interesting. Didn't know that about sqlite. If I summarize: Oracle: Locks only inserted row. Mysql: Locks entire table. sqlite: Locks entire DB. Also no network connectivity. Only for all-in-one box installations. I will be doing new installations to clients. My responsibility ends in recommending a suitable DB and building the appropriate support in kannel. The way I see it, it is between Postgres (for heavier traffic) and Mysql (faster, lighter load). SQLBox is descent, too, but I try to avoid Windows servers. Thanx, Nikos ----- Original Message ----- From: "Alejandro Guerrieri" <[email protected]> To: "Nikos Balkanas" <[email protected]> Cc: "sangprabv" <[email protected]>; "Jarek Guzik" <[email protected]>; <[email protected]> Sent: Thursday, January 22, 2009 4:15 PM Subject: Re: DLR DB processing Most of my experience is with MySQL. You have to keep in mind that DLR's and also SqlBox use rather simple queries and no complex locking is involved, so most DB perform decently well for this. I wouldn't go sqlite for moderate/heavy traffic because each request locks the whole DB, though. I've used MySQL for years without a single problem. Others report the same with Postgres. Oracle and others are less popular, but should perform equally I think. My advice: use whatever you're already supporting on your company. The benefits of using a platform that you already now beats any performance difference you may gain by switching to any other DB engine. Regards, -- Alejandro Guerrieri [email protected] On 19/01/2009, at 2:15, Nikos Balkanas wrote: Hi, Still counting votes. For heavy traffic seems to be Postgress. SQLBox is pretty descent, but I am not too thrilled about the OS. Windows has a documented 30% latency on its TCP/IP stack over Linux. For light traffic it is between MySQL and sqllite. Note that this is *only* for the internal kannel DLR storage. Alej, what do you say? BR, Nikos ----- Original Message ----- From: "sangprabv" <[email protected]> To: "Jarek Guzik" <[email protected]> Cc: "Nikos Balkanas" <[email protected]>; <[email protected]> Sent: Friday, January 16, 2009 11:01 AM Subject: Re: DLR DB processing So what is the best DB for DLR then? Suggestion please. TIA Willy -----Original Message----- From: Jarek Guzik <[email protected]> To: Nikos Balkanas <[email protected]> Cc: [email protected] Subject: Re: DLR DB processing Date: Fri, 16 Jan 2009 08:46:16 +0100 In this case you are right, use of oracle only for the storage of the DLR queue is kind of abuse. In my case there is also big delivery reporting database so at this point it make sense. Regards, Jaroslaw Guzik 2009/1/16 Nikos Balkanas <[email protected]>: Thanx Jareed, I find Oracle a bit overkill for just DLR storage. Mind you I didn't mean end point of the final DLR, just kannel's internal DLR storage. I was kind of hoping to get some input from Alex about sqllite. BR, Nikos ----- Original Message ----- From: <[email protected]> To: "'Nikos Balkanas'" <[email protected]>; <[email protected]> Sent: Thursday, January 15, 2009 10:27 PM Subject: RE: DLR DB processing Hi Nikos, I went poorly programming daemon which acquired DLR communicates in PERL, on the other hand, PHP script has been a bottleneck. Currently, with access to the oracle database and a bit of experience in the pl/sql I use oracle and mod_owa with apache, performance is suitable for me - I am able to take about 1000 DLRs within a few seconds. Also it is a convenient solution - all logic DLR of receiving can be drawn by oracle procedure. Regards, Jarek Guzik ________________________________________ From: Nikos Balkanas [mailto:[email protected]] Sent: Thursday, January 15, 2009 7:03 PM To: [email protected] Subject: DLR DB processing Hi, I am considering using a DB for DLR storage. Up till now I was using internal DLRs. Of the many options supported, (Mysql, PostgresSQL, Oracle, LibSdb, sqlbox, sqllite) which one would you consider best suited for bulk SMS, in terms of performance and reliability. If you could also give a one liner for your choice, it would be most appreciated. I thing it is fair to say, that internal is the fastest and least reliable of all. Thanx Nikos
