----- Original Message ----- > From: "Steven Roberts" <[email protected]> > To: "Michael Hrivnak" <[email protected]> > Cc: "Ryan Bowlby" <[email protected]>, [email protected] > Sent: Friday, April 12, 2013 1:19:43 PM > Subject: Re: [Pulp-list] WSGI processes / threads optimal? > > On Fri, Apr 12, 2013 at 10:23:17AM -0400, Michael Hrivnak wrote: > > The WSGI app that comes with Pulp serves the REST API only, and it is > > important that it run in only one process. It may be appropriate to > > use more than 8 threads, so feel free to tune that. The REST API is > > generally expected to be pretty low-traffic, mostly just handling > > requests from the "pulp-admin" command line tool. > > doesn't that wsgi process also handle things like scheduled repo sync's? > > that was what it looked like from a pulp user perspective at least... > > > that is the one that prior to the 2.1 beta series ate a bunch of RAM > during manual and scheduled repo syncs... > > Steve >
That is correct. What I was trying to say is that the only HTTP requests served by that process are those for the REST API. That process also carries out actions like repo syncs, dispatches commands to consumers, etc. Michael _______________________________________________ Pulp-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/pulp-list
