Fast proxy
in [Ruby]
|
From: Diego Bernardes on 12 Aug 2010 09:31 Today i have a application that send mails and this applications need to know when the user has opened the mail, its kind easy do this sending a id in some image file requested from the user mail(src="www.sample.com/image&id=1212"). But this need to be veryyyy fast. Actually testing on my notebook, apache could serve some image 7000 times a second, using em-proxy poiting to the same apache server, i could only get 2000 times a second, and i did nothing on em-proxy, just get from one side and send to another. Have any way to this faster? -- Posted via http://www.ruby-forum.com/.
From: Diego Bernardes on 12 Aug 2010 10:26 Diego Bernardes wrote: > Today i have a application that send mails and this applications need to > know when the user has opened the mail, its kind easy do this sending a > id in some image file requested from the user > mail(src="www.sample.com/image&id=1212"). > > But this need to be veryyyy fast. > > Actually testing on my notebook, apache could serve some image 7000 > times a second, using em-proxy poiting to the same apache server, i > could only get 2000 times a second, and i did nothing on em-proxy, just > get from one side and send to another. > > > Have any way to this faster? forgot to say, and taking that id and inserting into redis reduce the performance to 1500 req/s -- Posted via http://www.ruby-forum.com/.
From: Kirk Haines on 12 Aug 2010 11:00 On Thu, Aug 12, 2010 at 8:26 AM, Diego Bernardes <di3go.bernardes(a)gmail.com> wrote: >> Actually testing on my notebook, apache could serve some image 7000 >> times a second, using em-proxy poiting to the same apache server, i >> could only get 2000 times a second, and i did nothing on em-proxy, just >> get from one side and send to another. >> >> >> Have any way to this faster? > > forgot to say, and taking that id and inserting into redis reduce the > performance to 1500 req/s One can proxy very, very fast with Ruby and EM. Fast enough that messing with redis will, by a long shot, be your bottleneck. I suggest not doing it that way if you need really high speeds. Were it me, I'd write a simple server to itself return the image, and I'd throw records of images served into a log. That lets you decouple serving the image with recording it in redis, and it makes it trivial to break that task up into multiple pieces, or take advantage of off-peak times to catch up on data loading if your peak times actually serves images faster than the data can be stuffed into redis. Kirk Haines
From: Brian Candler on 12 Aug 2010 16:42 Kirk Haines wrote: > Were it me, I'd write a simple server to itself return the image, and > I'd throw records of images served into a log. Just parse the Apache logs. Or, if you want it more real-time, you can use the pipe log capability of Apache, so you can have a persistent Ruby process which receives the logs on stdin. But then again, you might as well just receive the HTTP in Ruby. Note: you should be aware that most modern E-mail clients *don't* open remote images in E-mails, for exactly the reason that it gives away information about them being read (*) Also: if you send out one million E-mails, *and* all of them are opened within a 24 hour period, *and* 20% of the users have old clients which do open remote images, then you'd only have to handle an average of 2.3 hits per second. Hardly need the world's fastest webserver for that. Regards, Brian. (*) And hence HTML E-mails with images usually now embed the images within the message, e.g. RFC2557, RFC2392 -- Posted via http://www.ruby-forum.com/.
From: Diego Bernardes on 13 Aug 2010 10:06 Thanks all for the help. Thanks for the tip Kirk, im gonna parse the log, its easier and faster, the applications isnt real time, i have time to process the log. The log files gonna rotate every hour, gonna process one file per hour. I also find something usefull, x-sendfile, i didint know that, this was the reason i was getting so "slow" req/s using ruby, i think using this with sinatra i could get near req/s as apache. Brian, About that, yes, its true, most mail block external images. But is the only way i can know if the user has read or not the mail. And the list is send to people who wants the mail, they trust in the mail content. Have any other way to track the mails? Again, thanks. Diego Bernardes -- Posted via http://www.ruby-forum.com/.
|
Next
|
Last
Pages: 1 2 Prev: Jquery_rails3 1.4.2 beta1 released Next: Why am I not getting the expected output? |