I'll try to build it in the weekend and test it out: I didn't read the fine prints of the uwsgi license but for all the "intranet" kind of apps where the included webserver can start to show its limits we could potentially download the latest stable windows binary and mount web2py on it.
Actually, I think I'll make a recipe to automate it "ala" https://github.com/web2py/web2py/blob/master/scripts/setup-web2py-nginx-uwsgi-ubuntu.sh , without the nginx part: it could be fine for all kinds of loads that are not extreme, and multiplatform.... On Friday, March 15, 2013 12:04:48 PM UTC+1, Roberto De Ioris wrote: > > > > I was missing the windows build option totally.... If speeds between > unix > > and Windows are at least on the same scale it can solve the > > mother-of-all-issues of windows deployments of python apps without using > > apache or iis. > > > > > I was not able to make some serious benchmark as all of the windows > machines i have are virtualized systems. > > From what i can measure the cygwin translation has a 10-15% impact in some > area (mainly in startup phases so it is nothing relevant), but we plan to > rewrite some critical part using the native windows api (we have already > done that for the locking part that instead of pthreads uses windows > mutexes). > > Another limit i have not investigated is windows select() implementation > (on the others posix system we use more modern event facilities). But i > suppose until you do not use it with hundreds of concurrent file > descriptors you should not experiment problems. > > -- > Roberto De Ioris > http://unbit.it > -- --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
