我们有项目针对性的.NET 2.0 RTM（是的，它应该是.NET 2.0 RTM，我们有一些正统的客户端）。而我只是想知道什么是ReaderWriterLock?为什么会如此糟糕，每个人都知道不使用它，试着用别的东西像锁定语句？如果我们可以使用.NET 3.5，我肯定会使用ReaderWriterLockSlim,但与 ReaderWriterLock 我是一个有点吓人所有这些来自世界各地的警示未来。衡量是否有人性能或什么？如果有一些性能问题，在什么样的有效载荷可我们所碰到的？

We have project targeted .NET 2.0 RTM (yes, it should be .NET 2.0 RTM, we have some orthodox clients). And I'm just wondering what are the downsides of ReaderWriterLock? Why is it so bad that everyone tell "don't use it, try to use something else like lock statement"? If we could use .NET 3.5, I would definitely use ReaderWriterLockSlim, but with ReaderWriterLock I'm a little scary with all these warning coming from everywhere. Does anybody measured performance or whatever? If there are some performance issues, under what payload can we encounter them?

我们有一个典型的情况， ReaderWriterLock 的主要目的，即多次读取和写入很少的条款。使用锁定语句会阻止所有的读者。也许这不是我们的一个可怕的问题，但如果我可以使用 ReaderWriterLock 我会更满意。 IMO引入多个监视器确实是一个非常非常糟糕的主意。

We have a classic situation in terms of ReaderWriterLock main purpose, i.e. multiple reads and rarely writes. Using lock statement would block all readers. Perhaps it's not an awful issue for us, but if I could use ReaderWriterLock I would be more satisfied. IMO introducing several monitors is a very very bad idea indeed.

推荐答案

以下几个职位可以为您提供您所期待的。想法

Following few posts can provide you the ideas you are looking for.

Performance ReaderWriterLockSlim与ReaderWriterLock

波多黎各马里亚尼的使用ReaderWriterLock部分这篇文章解释了一些成本和场景使用ReaderWriterLock，还要检查第1部分和< A HREF =htt​​p://blogs.msdn.com/b/ricom/archive/2006/05/12/596407.aspx>第2部分

Rico Mariani on Using ReaderWriterLock part this post explains some of the costs and scenarios to use ReaderWriterLock, also check part 1 and part 2

杰弗里里希特上替代ReaderWriterLock