c# - What are the real downsides of using ReaderWriterLock -


we have project targeted .net 2.0 rtm (yes, should .net 2.0 rtm, have orthodox clients). , i'm wondering downsides of readerwriterlock? why bad tell "don't use it, try use else lock statement"? if use .net 3.5, use readerwriterlockslim, readerwriterlock i'm little scary these warning coming everywhere. measured performance or whatever? if there performance issues, under payload can encounter them?

we have classic situation in terms of readerwriterlock main purpose, i.e. multiple reads , writes. using lock statement block readers. perhaps it's not awful issue us, if use readerwriterlock more satisfied. imo introducing several monitors very bad idea indeed.

following few posts can provide ideas looking for.

performance comparison of readerwriterlockslim readerwriterlock

rico mariani on using readerwriterlock part post explains of costs , scenarios use readerwriterlock, check part 1 , part 2

jeffrey richter on alternative readerwriterlock


Comments

Popular posts from this blog

php - What is the difference between $_SERVER['PATH_INFO'] and $_SERVER['ORIG_PATH_INFO']? -

fortran - Function return type mismatch -

queue - mq_receive: message too long -