If you need speed (store more than 100 > records per second, give a look to 'INSERT DELAYED' (only MyISAM)
later I will suggest to first normalize the DB, and based on your queries made by your frontend/application crete your indexes. either MyISAM/INODB *sql, you will need to implement a queue system just in case DB goes down and you don't wan to lose any message, for a very simple queue system (only mysql) you could give a try to http://code.google.com/p/dalmp/ check the SQL queues feature. regards. On Thu, Mar 22, 2012 at 7:29 PM, spameden <spame...@gmail.com> wrote: > mysql> show indexes from kannel.dlr; > +-------+------------+---------------------+--------------+-------------+-----------+-------------+----------+--------+------+------------+---------+---------------+ > | Table | Non_unique | Key_name | Seq_in_index | Column_name | > Collation | Cardinality | Sub_part | Packed | Null | Index_type | Comment | > Index_comment | > +-------+------------+---------------------+--------------+-------------+-----------+-------------+----------+--------+------+------------+---------+---------------+ > | dlr | 0 | smsc_ts_destination | 1 | smsc | > A | 1 | 15 | NULL | YES | BTREE | > | | > | dlr | 0 | smsc_ts_destination | 2 | ts | > A | 9408 | 35 | NULL | YES | BTREE | > | | > | dlr | 0 | smsc_ts_destination | 3 | destination | > A | 9408 | 11 | NULL | YES | BTREE | > | | > | dlr | 0 | url | 1 | url | > A | 9408 | 16 | NULL | YES | BTREE | > | | > +-------+------------+---------------------+--------------+-------------+-----------+-------------+----------+--------+------+------------+---------+---------------+ > 4 rows in set (0.02 sec) > > CREATE index smsc_ts_destination ON dlr (smsc(15), ts(35), destination(11)) > CREATE index url ON dlr (url(16)) > > > 2012/3/22 Ashish Agarwal <ashisha...@gmail.com> >> >> Hello, >> >> Thanks for your response. What are the fields that should be indexed? >> >> >> On Fri, Mar 23, 2012 at 12:54 AM, spameden <spame...@gmail.com> wrote: >>> >>> We are using InnoDB. It works just fine with dlr and send_sms, sent_sms >>> tables. InnoDB comparing to MyISAM is more fault proof, so I'd recommend >>> using it, every insert is a transaction, so theoritacally you won't lose >>> more than 1 transaction if something bad happens. >>> >>> Don't forget to add relevant indexes for speeding up queries from dlr >>> table. >>> >>> >>> 2012/3/22 Ashish Agarwal <ashisha...@gmail.com> >>>> >>>> Hello, >>>> >>>> I wish to know what is the suitable mysql engine(MYISAM or INNODB) for >>>> dlr and sqlbox (send_sms and sent_sms table) from kannel. I currently have >>>> high load of traffic and RAM is not a problem. >>>> >>>> Please suggest. >>>> >>>> -- >>>> Regards, >>>> >>>> Ashish >>> >>> >> >> >> >> -- >> Regards, >> >> Ashish Agarwal > >
