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 > >
