blocks|key|4117904|text|测试多线程代码非常困难，因此您应该通过编写多线程应用程序的经验丰富的同事的详细代码审查来补充您的测试。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4117905|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

It is very difficult to test multi-threaded code, so you should supplement your tests with a detailed code review by colleagues experienced in writing multi-threaded applications.

blocks|key|4118043|text|确保你在一台真正有多个CPU的机器上进行压力测试，这通常会比在一台CPU机器上发现更多的多线程问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4118044|然后在64位、更快的CPU、更多的CPU等机器上测试它。|4118045|正如@onebyone.livejournal.com所说，使用具有非一致性内存缓存的机器；尽管根据NUMA+article+on+Wikipedia的说法，这可能很难找到。|offset|length|4118046|当然，在尽可能多的不同机器上使用代码不会有什么坏处，也是发现问题的好方法。|4118047|entityMap|0|LINK|mutability|MUTABLE|url|http://en.wikipedia.org/wiki/Non-Uniform_Memory_Access#Cache_coherent_NUMA_.28ccNUMA.29^0|0|0|1E|P|0|0|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|S|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|T|8|@]|9|@$F|U|G|V|1|W]]|A|$]]|$1|H|3|I|5|6|7|X|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|Y|8|@]|9|@]|A|$]]]|K|$L|$5|M|N|O|A|$P|Q]]]]

Make sure you try your stress test on a machine that truly has multiple CPU's. That will usually uncover more multithreaded problems than anything run on a single CPU machine.

Then test it on machines that are 64-bit, faster CPUs, more CPUs, etc.

And as @onebyone.livejournal.com says, use a machine with non-coherent memory caches; although, according to the <a href="http://en.wikipedia.org/wiki/Non-Uniform_Memory_Access#Cache_coherent_NUMA_.28ccNUMA.29" rel="nofollow noreferrer">NUMA article on Wikipedia</a>, that may be difficult to find.

Certainly using the code on as many different machines as possible can't hurt, and is also a good way to uncover issues.

blocks|key|899609|text|我猜您可以从查看良好的代码中包含的测试开始。例如，GNU+libc+(nptl)的pthread实现包括读写锁和一些测试。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|899610|$+ls+nptl/tst-rwlock*
nptl/tst-rwlock1.c
nptl/tst-rwlock10.c
nptl/tst-rwlock11.c
nptl/tst-rwlock12.c
nptl/tst-rwlock13.c
nptl/tst-rwlock14.c
nptl/tst-rwlock2.c
nptl/tst-rwlock3.c
nptl/tst-rwlock4.c
nptl/tst-rwlock5.c
nptl/tst-rwlock6.c
nptl/tst-rwlock7.c
nptl/tst-rwlock8.c
nptl/tst-rwlock9.c|code-block|syntax|javascript|899611|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

I guess that you can start by looking at tests included in well-established code. For example the pthreads implementation of GNU libc (nptl) includes read-write locks and some tests.

<pre><code>$ ls nptl/tst-rwlock*
nptl/tst-rwlock1.c
nptl/tst-rwlock10.c
nptl/tst-rwlock11.c
nptl/tst-rwlock12.c
nptl/tst-rwlock13.c
nptl/tst-rwlock14.c
nptl/tst-rwlock2.c
nptl/tst-rwlock3.c
nptl/tst-rwlock4.c
nptl/tst-rwlock5.c
nptl/tst-rwlock6.c
nptl/tst-rwlock7.c
nptl/tst-rwlock8.c
nptl/tst-rwlock9.c
</code></pre>

blocks|key|13252|text|如果您能够在工作代码中使用Boost，则应该使用shared_mutex类，它实现了读/写锁定。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|13253|即使它不能100%25满足您的需求，您也应该将代码中的思想用于您的代码，并且，如果Boost代码有针对shared_mutex的测试(我还没有检查过)，您应该将它们添加到您拥有的测试中。|13254|entityMap|0|LINK|mutability|MUTABLE|url|http://www.boost.org/doc/libs/1_39_0/doc/html/thread/synchronization.html#thread.synchronization.mutex_types.shared_mutex^0|O|C|O|C|0|0|1D|C|0^^$0|@$1|2|3|4|5|6|7|P|8|@$9|Q|A|R|B|C]]|D|@$9|S|A|T|1|U]]|E|$]]|$1|F|3|G|5|6|7|V|8|@$9|W|A|X|B|C]]|D|@]|E|$]]|$1|H|3|-4|5|6|7|Y|8|@]|D|@]|E|$]]]|I|$J|$5|K|L|M|E|$N|O]]]]

If you are able to use Boost in your work code at all, you should use the <a href="http://www.boost.org/doc/libs/1_39_0/doc/html/thread/synchronization.html#thread.synchronization.mutex_types.shared_mutex" rel="nofollow noreferrer"><code>shared_mutex</code></a> class, which implements read/write locking.

Even if it doesn't 100% suit your needs, you should use the ideas in the code for your code, and, if the Boost code has tests for the <code>shared_mutex</code> (I haven't checked), you should add them to the tests you have.

blocks|key|13120|text|通常，我会提供避免实现自己的锁的指导，除非你已经证明现有的稳定的实现不能满足你的性能需求。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|13121|测试和构建同步原语可能会很棘手，而且不直观。|13122|使用boost::shared_mutex的指导是非常明智的，如果您使用的是Win32平台，我会尽可能地引导您使用Slim+Reader+Writer+Locks，因为它们健壮且快速。|offset|length|13123|虽然它对今天的生产产品没有帮助，但在Visual+Studio2010Beta1中，我们添加了一个reader_writer+class，虽然它不是跨平台的，但它将成为VS2010+redist的一部分。|13124|entityMap|0|LINK|mutability|MUTABLE|url|http://msdn.microsoft.com/en-us/library/aa904937(VS.85).aspx|1|http://msdn.microsoft.com/en-us/library/dd504907(VS.100).aspx^0|0|0|1L|O|0|0|1D|J|1|0^^$0|@$1|2|3|4|5|6|7|T|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|U|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|V|8|@]|9|@$F|W|G|X|1|Y]]|A|$]]|$1|H|3|I|5|6|7|Z|8|@]|9|@$F|10|G|11|1|12]]|A|$]]|$1|J|3|-4|5|6|7|13|8|@]|9|@]|A|$]]]|K|$L|$5|M|N|O|A|$P|Q]]|R|$5|M|N|O|A|$P|S]]]]

Generally I would offer guidance to avoid implementing your own locks, unless you have proven than an existing and stable implementation doesn't meet your performance needs.

Testing and building synchronization primitives can be tricky and non intuitive.

The guidance to use boost::shared_mutex is quite wise, if you're on the Win32 platform I would guide you to use the <a href="http://msdn.microsoft.com/en-us/library/aa904937(VS.85).aspx" rel="nofollow noreferrer">Slim Reader Writer Locks</a> if possible because they are robust and fast.

Though it won't help for a production product today, in Visual Studio 2010 Beta 1 we've adding a <a href="http://msdn.microsoft.com/en-us/library/dd504907(VS.100).aspx" rel="nofollow noreferrer">reader_writer class</a> which while not cross platform will be part of the VS2010 redist.

blocks|key|13156|text|既然你已经实现了读/写锁，那么显然你应该在多线程环境中测试它。当没有写操作时，诸如多个读线程之类的测试场景不应该被阻塞，并且在几个小时内运行数千个读/写操作应该不会导致死锁，这可能是一个好的开始。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|13157|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

since you've implemented a read/write lock then obviously you should test it in multi-threading environment. Test scenarios such as multiple reading threads should not be blocked when there are no write operations and running thousands of read/write operations over several hours should not cause deadlock might be a good start.

blocks|key|1313704|text|运行两个线程，这两个线程都执行此操作|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1313705|++long+long+int+j+=+0;
++long+long+int+oldJ+=+0;
++while+(true)
++{
++++++for+(long+long+int+i+=+0;+i+<=+100000;+%2B%2Bi)+
+++++++//+try+and+make+it+64+bits+to+be+sure+its+non-atomics+:)
++++++{+++++++
++++++++++oldJ+=+j;++++++
++++++++++YourRead(j)+//+read+in+j
++++++++++assert(j+==+(oldJ+%2B+1));
++++++++++SleepSomeRandomPeriod(++);
++++++++++YourWrite(i)
++++++++++SleepSomeRandomPeriod(++);
++++++}
++}|code-block|syntax|javascript|1313706|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

Run two threads that both do this

<pre><code> long long int j = 0;
 long long int oldJ = 0;
 while (true)
 {
 for (long long int i = 0; i &lt;= 100000; ++i) 
 // try and make it 64 bits to be sure its non-atomics :)
 { 
 oldJ = j; 
 YourRead(j) // read in j
 assert(j == (oldJ + 1));
 SleepSomeRandomPeriod( );
 YourWrite(i)
 SleepSomeRandomPeriod( );
 }
 }
</code></pre>

blocks|key|13224|text|经常使用ASSERT/assert来测试您的所有假设，并检查前置和后置条件。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|13225|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Use ASSERT/assert often to test all of your assumptions and to check pre and post conditions.

blocks|key|1313763|text|IBM有an+analysis+tool+for+detecting+threading+issues+in+Java。也许C%2B%2B也有类似的东西？|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1313764|entityMap|0|LINK|mutability|MUTABLE|url|http://www.alphaworks.ibm.com/tech/mtrat^0|4|1J|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

IBM have <a href="http://www.alphaworks.ibm.com/tech/mtrat" rel="nofollow noreferrer">an analysis tool for detecting threading issues in Java</a>. Perhaps there is something similar for C++?

blocks|key|13140|text|请确保在具有多个CPU核心的计算机上进行测试，或者至少在具有超线程的CPU上进行测试。多线程存在许多问题，这些问题只有在线程真正在不同CPU上并行运行时才会出现，或者会更频繁地出现。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|13141|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Make sure you test on a machine with multiple CPU cores or at least a CPU with hyperthreading. There are many problems with mulitiple threads that only occur, or that occur much more frequently when threads are really running on parallel on different CPUs.

As part of a project at work, I implemented a Read/Write lock class in C++. Before pushing my code to production, what sort of tests should I run on my class to be sure it will function correctly. 

I've obviously performed some sanity tests on my class (making sure only one writer can access at a time, making sure releases and claims increment and decrement properly, etc.)

I'm looking for tests that will guarantee the stability of my class and to prevent edge cases. It seems testing multi-threaded code is much harder than standard code.

Read/Write Locks

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

教程

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云智能顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

EdgeOne AI 安全实战专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

聚焦“写作效率、视觉美观与运行性能”三方面进行全面升级，为您提供更高效、稳定的创作环境

社区富文本&Markdown编辑器全新改版上线，欢迎大家体验!

诚挚邀请您参与本次调研，分享您的真实使用感受与建议。您的反馈至关重要，感谢您的支持与参与！

社区新版编辑器体验调研

作为工作项目的一部分，我用C++实现了一个读/写锁类。在将我的代码推向生产之前，我应该在我的类上运行哪种类型的测试，以确保它将正常工作。显然，我已经在我的类上执行了一些健全性测试(确保一次只有一个编写器可以访问，确保发布和声明正确地递增和递减，等等)。我正在寻找能够保证我的类的稳定性并防止边缘情况的测试。测试多线程代码似乎比标准代码难得多。

问读/写锁
EN

回答 10

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问读/写锁EN

回答 10

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问读/写锁
EN