Hello, we want to process 7000 to 10000 message and store it to the Database perminute. we are trying through threads. can you please help me how we do? Regards Kaja Mohaidee.A Trichy
on 14.08.2008 07:30
on 14.08.2008 09:13
Hi Kaja, can we get a little more details?! "Messages" meaning what? http- requests? Storing what? You already checked out merb (which has an edge over rails when it comes to multithreading), especially merb- core, which strips out all overhead: And it is not fast enough for you? Maybe you are willing to go even more low-level with thin? And you are still sure, that it has to be ruby? Erlang has a reputation for handling concurrency very well and is very good at exploiting multi-core-machines (now we are talking about low-level....) Cheers stf Am 14.08.2008 um 07:30 schrieb Kaja Mohaideen:
on 14.08.2008 10:59
Stefan Frank wrote: > Hi Kaja, > > can we get a little more details?! "Messages" meaning what? http- > requests? Storing what? You already checked out merb (which has an > edge over rails when it comes to multithreading), especially merb- > core, which strips out all overhead: And it is not fast enough for > you? Maybe you are willing to go even more low-level with thin? And > you are still sure, that it has to be ruby? Erlang has a reputation > for handling concurrency very well and is very good at exploiting > multi-core-machines (now we are talking about low-level....) > > Cheers > stf > > > > > Am 14.08.2008 um 07:30 schrieb Kaja Mohaideen: HI it is for send and receive SMS . we are storing some content on queue like message . for example 10000 message will come to queue per min. at that time we get 1000 messages and want to store 1000 messages to the database. so we want to go thread. how we implement for this through thread
on 14.08.2008 11:00
Stefan Frank wrote: > Hi Kaja, > > can we get a little more details?! "Messages" meaning what? http- > requests? Storing what? You already checked out merb (which has an > edge over rails when it comes to multithreading), especially merb- > core, which strips out all overhead: And it is not fast enough for > you? Maybe you are willing to go even more low-level with thin? And > you are still sure, that it has to be ruby? Erlang has a reputation > for handling concurrency very well and is very good at exploiting > multi-core-machines (now we are talking about low-level....) > > Cheers > stf > > > > > Am 14.08.2008 um 07:30 schrieb Kaja Mohaideen: HI it is for send and receive SMS . we are storing some content on queue like message . for example 10000 message will come to queue per min. at that time we get 1000 messages and want to store 1000 messages to the database. so we want to go thread. how we implement for this through thread
on 14.08.2008 11:30
again the question: Why RoR? What is your environment? I do not want to drive you away from ror, but erlang has a strong standing in the telco-industry and searching for "erlang sms" in google brings up 252.000 hits. If you are only concerned with the sms-part and the speed, you should check out erlang. Otherwise you should bring up some more requirements, that have to do more with rails (and by the way: with the purpose of this list). cheers Stefan Am 14.08.2008 um 11:00 schrieb Kaja Mohaideen:
on 14.08.2008 11:43
Kaja, since you asked the same question on RubyTalk, we assume this is more of a Ruby-ish question than it is about Rails. Nicolai