Date: Wed, 28 Apr 2010 07:11:09 -0700 From: Alfred Perlstein <alfred@freebsd.org> To: Karl Pielorz <kpielorz_lst@tdx.co.uk> Cc: freebsd-threads@FreeBSD.org Subject: Re: Advice / best practice - thread connection pools / mutexes Message-ID: <20100428141109.GL35381@elvis.mu.org> In-Reply-To: <BA117CBD0D3A7158C40514FE@HPQuadro64.dmpriest.net.uk> References: <6AD0A971B01FA1DE632BAF65@HPQuadro64.dmpriest.net.uk> <20100428111226.GK35381@elvis.mu.org> <BA117CBD0D3A7158C40514FE@HPQuadro64.dmpriest.net.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
* Karl Pielorz <kpielorz_lst@tdx.co.uk> [100428 04:56] wrote: > > --On 28 April 2010 04:12 -0700 Alfred Perlstein <alfred@freebsd.org> wrote: > > >The most simple method is to do the following at startup: > > > >[snip wonderful sample code] > > > >This should provide for a connection pool, each thread > >can then call get_con() to get a connection, and should > >call put_con() when done with it. > > > >good luck. > >-Alfred > > Thanks, that looks pretty much exactly what I'm looking for - thanks also > to the other people who replied, I've certainly got a few options now > (which is a big improvement on what I had before!). I'd keep an eye out for Kip's version, it's likely to be a lot faster. :) -- - Alfred Perlstein .- AMA, VMOA #5191, 03 vmax, 92 gs500, 85 ch250, 07 zx10 .- FreeBSD committer
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20100428141109.GL35381>