Dave, don't know if you're thinking of the same thing I have in mind, but I'd also like to see a policy where round-robin is used, however, the new backend is not selected on existing connection from client for new requests.
Currently, if a client makes a request for a page, and that page has other dependent files (css, js,images) which are requested on the keep-alive connection, pound will try to randomly select a new backend after initial request. I'd like to have a session type where pound selects a backend randomly on a new request, and if a "Connection: keep-alive" is provided by the client, for pound to reuse the connection to the initial backend (assuming the service is the same). This would cut down on the number of connections being opened/closed to backends on the request from the same client. Albert On 12/30/2011 10:48 AM, Dave Steinberg wrote: > On 12/30/2011 9:44 AM, Robert Segall wrote: >> Hallo everybody >> >> New year, new version: we declare open the wish-list for 2.7 features. >> Please reply to this with your list of enhancements/patches/wishes. >> >> Please feel also free to offer comments (supportive or not, as the case >> may be) on items that others may post. The more support for a feature, >> the better its chances of making it into 2.7. >> >> Please do NOT post patches in reply - a short description is quite >> enough. You can mail me directly if you want to offer patches. > > Some notion of configurable backend-selection policy. The default, > round-robin can stay, but I'd like the option of 'least connections' > too. It would be configured globally or on the service level. > > The 'priority' mechanism isn't my favorite, it requires manual > adjustment, but 'least connections' basically tunes itself constantly. > > Regards,
