On Sun, Sep 15, 2019 at 11:34 AM Mike Orr <[email protected]> wrote: > Regarding performance, I usually use Waitress but I hvae one > application that's higher-volume than the others and it bogged down in > stress tests but when we switched it to uWSGI the problems went away. > The downside is uWSGI is C so it's harder to install: it may be easy > on one server/OS but not on another, and if the environment doesn't > have the C build tools you have to install them. Recently we migrated > the application to Docker although I don't think we migrated uWSGI so > it may be back to Waitress. I started thinking about looking at Docker > uWSGI options but haven't pursued it yet.
One problem with uWSGI is poor documentation. It has a lot of configuration options and their documentation is sometimes hard to understand and there's no place to go "How do I do this?" or "Which options are relevant to this?" And in one case the documentation was wrong. There's an option to read a logging config from a PasteDeploy INI file but it didn't work. So as a workaround I added a setting in my application, 'log = %(__file__)s' (or maybe the value was %(here)s/production.ini'), and if it's set then I call 'logging.config.fileConfig()' on it. (Or 'pyramid.paster.setup_logging()'.) -- Mike Orr <[email protected]> -- You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/pylons-discuss/CAH9f%3Duo9fJMhq1m2CKuvpvF3A8Kz0mcxiKEsvPJNp0p3VS3%2Bsw%40mail.gmail.com.
