On Wed, Feb 11, 2015 at 11:15:28AM -0500, Arran Cudbard-Bell wrote:
On 11 Feb 2015, at 11:08, Phil Mayers <p.mayers@IMPERIAL.AC.UK> wrote:
Sorry, not what I meant - rather the figure "32kb" for each REQUEST. Some sites might allocate a lot of crap in their configs, others little, so it might be something to vary.
But it's probably pointless optimisation!
It's already configurable (shhh, don't tell anyone). But it's one of those knobs that really shouldn't exist, and should be determined automatically by the server.
Is there any reason why the server can't keep track of the average size of the last <n> requests, and dynamically adjust the amount of memory it allocates for the request pool? Not sure if there is a way in, say, talloc free to find out how much memory was actually freed in total? Then it would be an easy job at free time to keep track of how much was used for that request, and feed back into a loop to determine the allocation size. But maybe it's just overcomplicating things. Worst case you don't want the situation that most requests go 10 octets over 32k - so some debug or similar to tell the admin this has happened would be useful. Matthew -- Matthew Newton, Ph.D. <mcn4@le.ac.uk> Systems Specialist, Infrastructure Services, I.T. Services, University of Leicester, Leicester LE1 7RH, United Kingdom For IT help contact helpdesk extn. 2253, <ithelp@le.ac.uk>