Just a little questions guys: when a user upload a file to server, and that file is a litte big and takes 3 seconds to be uploaded... what's the proper way, if possible, not to block the entire system for these 3 seconds so the server can serve other users while the upload is taking place.
On Wednesday, February 25, 2015 at 3:28:34 PM UTC+1, Tom Evans wrote: > > On Tue, Feb 24, 2015 at 11:30 PM, Benj <[email protected] <javascript:>> > wrote: > > Hi, > > i'm going to invest lots of time and energy in various web projects > (mostly > > community web sites), and want to pick up a language / framework and > invest > > heavily on it. > > I've spent a lot of time evaluating the various options, and narrowed my > > choice to 2 stacks: C sharp asp.net MVC or Python / Django. > > > > I'm more attracted to Python / Django combo, because of the Python > language, > > and high level framework Django. I really want to use these. > > My only concern is speed. I read that Python can't run concurrent tasks, > is > > this true ? So a multi-processor with hyperthreads won't benefit the > stack > > and even slow it down ? > > I have no clue how this translates in reality, but should I expect > noticable > > performance difference on a same server, shall I use Python / Django > than if > > I had C Sharp Asp.net ? > > I don't want to invest lots of time and efforts only to discover in the > end > > that the site is slow. > > You that have real world experiences with running sites, what are your > > conclusions ? > > > > > > I expect sites to be medium traffic: could be handled by a good > dedicated > > server or average cloud ressources. > > > > Benj > > Unless you are producing web-scale sites (gmail, ebay, instagram), the > speed of your website will depend more upon what you do with a > framework than the framework you choose. > > If you are producing web-scale sites, then whatever framework you > choose you will need to make the right design decisions and/or > compromises. > > Even with the best framework in the world, if you design the > architecture of a website poorly, the website will be slow. > > Even less important than the choice of framework is the choice of > hosting container for your framework. If you ever get to the point > where the speed of your wsgi container is the thing that is holding > you back, well done, now you should spend some time looking at it. > Until then, use the way that is easiest for you. > > Cheers > > Tom > -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/7e783c1f-2c44-4110-8dd9-933b489ac9ac%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
