Hey Micahel, Yes, I ran the tests locally in redis. I thought this would be the best choice for a 1-to-1 comparison. In my opinion, it would invalidate the results to run the tests on an outside server or service.
On Tuesday, September 13, 2016 at 7:13:04 AM UTC-4, Michael Manfre wrote: > > Hi Robert, > > Thanks for doing this load testing. More context would be useful to help > us outside observers to understand the potentially different variables. Is > redis running locally or are you using elasticache? > > Regards, > Michael Manfre > > On Mon, Sep 12, 2016 at 9:41 PM Robert Roskam <raider...@gmail.com > <javascript:>> wrote: > >> Hey Chris, >> >> The goal of these tests is to see how channels performs with normal HTTP >> traffic under heavy load with a control. In order to compare accurately, I >> tried to eliminate variances as much as possible. >> >> So yes, there was one worker for both Redis and IPC setups. I provided >> the supervisor configs, as I figured those would be helpful in describing >> exactly what commands were run on each system. >> >> Does that help bring some context? Or would you like for me to elaborate >> further on some point? >> >> Thanks, >> Robert >> >> >> >> On Monday, September 12, 2016 at 2:38:59 PM UTC-4, Chris Foresman wrote: >>> >>> Is this one worker each? I also don't really understand the implication >>> of the results. There's no context to explain the numbers nor if one result >>> is better than another. >>> >>> On Sunday, September 11, 2016 at 7:46:52 AM UTC-5, Robert Roskam wrote: >>>> >>>> Hello All, >>>> >>>> The following is an initial report of Django Channels performance. >>>> While this is being shared in other media channels at this time, I fully >>>> expect to get some questions or clarifications from this group in >>>> particular, and I'll be happy to add to that README anything to help >>>> describe the results. >>>> >>>> >>>> https://github.com/django/channels/blob/master/loadtesting/2016-09-06/README.rst >>>> >>>> >>>> Robert Roskam >>>> >>> -- >> You received this message because you are subscribed to the Google Groups >> "Django developers (Contributions to Django itself)" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to django-develop...@googlegroups.com <javascript:>. >> To post to this group, send email to django-d...@googlegroups.com >> <javascript:>. >> Visit this group at https://groups.google.com/group/django-developers. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/django-developers/7fdb4db1-7458-409f-94f5-d1dad3973616%40googlegroups.com >> >> <https://groups.google.com/d/msgid/django-developers/7fdb4db1-7458-409f-94f5-d1dad3973616%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> For more options, visit https://groups.google.com/d/optout. >> > -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/e5c17d4f-c3c4-444e-a654-69ab42dac8fe%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
