[Serusers] Which locking mechanism is useful for usrloc in production environment?

[Vaclav Kubart]

Hi,
it probably highly depends on your OS and kernel. 

I did performance testing on Debian linux with kernel 2.6.8 and it seems
to me, that all locking methods ("fast locking", sysV, pthreads, possix)
were approx. the same for "short" operations like transaction handling. 

I did another testing on Centos based distro, with kernel 2.6.9 for
"long" operations like usrloc with slow DB and there most of the locking
methods were the same (sys V, pthreads, possix) but the "fast locking"
was significantly worse!

So ... I know that I have to run these tests on the same machines etc,
but for the first look it seems to me that whatever locking method than
"fast locking" will be OK. But this can be valid for Linux and quite new
kernel only; I don't absolutely now what about other OS.

	Vaclav

On Thu, Feb 01, 2007 at 04:05:56PM +0530, Ramu Yadav wrote:
> Hello,
> 
> At present we are using "sys v semaphores"(USE_SYSV_SEM) for locking.
> 
> But we see a some delay while acquiring the lock to modify the usrloc's
> location table.
> 
> We are in a thought to use "posix semaphores" (USE_POSIX_SEM), will this
> improve any performance for usrloc location table.
> 
> Thoughts and Ideas will be appreciated.
> 
> -- 
> Ramu Yadav

> _______________________________________________
> Serusers mailing list
> Serusers at lists.iptel.org
> http://lists.iptel.org/mailman/listinfo/serusers