Alan> What I find a little odd is that there¹s so much memory Alan> lost. The server tries hard to clean up all memory on exit.
:-/
Alan> But it¹s odd that nothing¹s being cleaned up on exit. That Alan> makes it much harder to track down real errors.
What I found is that if I let it run for 50,000 requests or so, looking at the highest usage possibly lost and definitely losts blocks tended to show the current problem.
Ok, I'll change the config to make the sockets pretty short-lived and then launch into a 50,000-request loop? Will that be useful? Stefan Paetow Moonshot Industry & Research Liaison Coordinator t: +44 (0)1235 822 125 gpg: 0x3FCE5142 xmpp: stefanp@jabber.dev.ja.net skype: stefan.paetow.janet jisc.ac.uk Jisc is a registered charity (number 1149740) and a company limited by guarantee which is registered in England under Company No. 5747339, VAT No. GB 197 0632 86. Jisc¹s registered office is: One Castlepark, Tower Hill, Bristol, BS2 0JA. T 0203 697 5800. Jisc Collections and Janet Ltd. is a wholly owned Jisc subsidiary and a company limited by guarantee which is registered in England under Company No. number 2881024, VAT No. GB 197 0632 86. The registered office is: Lumen House, Library Avenue, Harwell, Didcot, Oxfordshire, OX11 0SG. T 01235 822200.