Re: [Webware-discuss] Why does ThreadedAppServer.addSocketHandler() write to disk?
Am 08.06.2010 23:20, schrieb Steve Schwarz: We are using Twisted to dispatch/maintain the Webware process pool. Will see about possibility of open sourcing our SingleThreadedAppServer and our twisted server as this progresses. Great. Maybe this can give us some ideas for a new native Webware app server. -- Christoph -- ThinkGeek and WIRED's GeekDad team up for the Ultimate GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the lucky parental unit. See the prize list and enter to win: http://p.sf.net/sfu/thinkgeek-promo ___ Webware-discuss mailing list Webware-discuss@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/webware-discuss
Re: [Webware-discuss] Why does ThreadedAppServer.addSocketHandler() write to disk?
Am 07.06.2010 22:00 schrieb Steve Schwarz: We are looking to run multiple Webware instances from a single Webware directory/checkout and can do so by providing configuration differences via command line args. Just out of curiosity, why do you want to do that? I'm usually running different instances from different working dirs only. But I noticed that ThreadedAppServer.addSocketHandler() creates files like http.address and adapter.address containing the address:port for each adapter: ... Can anyone explain the purpose? Trying to stop running multiple appservers on the same address/port? If so the port will already be bound so the appserver will fail... I think they are only used as a way to communicate the appserver port to some of the adapters, e.g. the CGIAdapter. If you start a second instance, the file should be overwritten with a warning, doesn't this work for you? If you don't want this, you can set a different name for it in the 2nd instance via the AppServer setting AddressFiles, e.g. '%s.address2' see http://www.webwareforpython.org/WebKit/Docs/Configuration.html#appserver-config -- Christoph -- ThinkGeek and WIRED's GeekDad team up for the Ultimate GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the lucky parental unit. See the prize list and enter to win: http://p.sf.net/sfu/thinkgeek-promo ___ Webware-discuss mailing list Webware-discuss@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/webware-discuss
Re: [Webware-discuss] Why does ThreadedAppServer.addSocketHandler() write to disk?
Am 08.06.2010 21:27 schrieb Steve Schwarz: We'd like to simplify our deployment. Now our admins have to install Webware multiple times for each appserver instance on multiple servers. It would be easier to just deploy once and have all instance refer to that one check out. Ok, as I understand, your working dir is on a shared directory? We also see better performance running with a pool of single threaded appservers instead of using the ThreadedAppServer. Are you using multi-core/multi-processing machines? -- Christoph -- ThinkGeek and WIRED's GeekDad team up for the Ultimate GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the lucky parental unit. See the prize list and enter to win: http://p.sf.net/sfu/thinkgeek-promo ___ Webware-discuss mailing list Webware-discuss@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/webware-discuss
Re: [Webware-discuss] Why does ThreadedAppServer.addSocketHandler() write to disk?
On Tue, Jun 8, 2010 at 2:35 PM, Christoph Zwerschke c...@online.de wrote: Am 08.06.2010 21:27 schrieb Steve Schwarz: We'd like to simplify our deployment. Now our admins have to install Webware multiple times for each appserver instance on multiple servers. It would be easier to just deploy once and have all instance refer to that one check out. Ok, as I understand, your working dir is on a shared directory? In the process pool install each server would have one checkout shared by 10-20 SingleThreadedAppServer Webware instances. We also see better performance running with a pool of single threaded appservers instead of using the ThreadedAppServer. Are you using multi-core/multi-processing machines? Yep. Looks like we are experiencing GIL contention on our compute heavy pages. Refactoring is also going on in the application to solve that problem. Steve -- ThinkGeek and WIRED's GeekDad team up for the Ultimate GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the lucky parental unit. See the prize list and enter to win: http://p.sf.net/sfu/thinkgeek-promo___ Webware-discuss mailing list Webware-discuss@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/webware-discuss
Re: [Webware-discuss] Why does ThreadedAppServer.addSocketHandler() write to disk?
Am 08.06.2010 21:44 schrieb Steve Schwarz: Yep. Looks like we are experiencing GIL contention on our compute heavy pages. Refactoring is also going on in the application to solve that problem. Adding an alternative to the MultiThreadedAppServer has been on my todo list for Webware for quite a while already (at least as long we're still running on Python 2 - the GIL may become less problematic with Py 3.2). Maybe a MultiProcessAppServer could be the alternative or somethin with an approach like Concurrence or Twisted. -- Christoph -- ThinkGeek and WIRED's GeekDad team up for the Ultimate GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the lucky parental unit. See the prize list and enter to win: http://p.sf.net/sfu/thinkgeek-promo ___ Webware-discuss mailing list Webware-discuss@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/webware-discuss
Re: [Webware-discuss] Why does ThreadedAppServer.addSocketHandler() write to disk?
On Tue, Jun 8, 2010 at 3:56 PM, Christoph Zwerschke c...@online.de wrote: Maybe a MultiProcessAppServer could be the alternative or somethin with an approach like Concurrence or Twisted. We are using Twisted to dispatch/maintain the Webware process pool. Will see about possibility of open sourcing our SingleThreadedAppServer and our twisted server as this progresses. Steve -- ThinkGeek and WIRED's GeekDad team up for the Ultimate GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the lucky parental unit. See the prize list and enter to win: http://p.sf.net/sfu/thinkgeek-promo___ Webware-discuss mailing list Webware-discuss@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/webware-discuss
