blocks|key|4592719|text|所有其他的答案都集中在通过测试代码并以某种形式实际运行它，或者礼貌地说“不要自己做，使用现有的库”来实际测试代码。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4592720|这是很棒的，但是IMO，最重要的(实际测试也很重要)测试是逐行查看代码，对于，每一行代码都会问“如果我在这里被另一个线程中断了会发生什么？”想象一下另一个线程，在这个中断期间运行几乎任何其他行/函数。事情还会保持一致吗？当竞争资源时，其他线程是否阻塞或旋转？|offset|length|style|BOLD|4592721|这就是我们在学校学习并发时所做的，这是一种令人惊讶的有效方法。总之，我觉得花时间向自己证明事情是一致的，并且在所有状态下都像预期的那样工作，这是你在处理这些东西时应该使用的第一个技术。|4592722|entityMap^0|0|12|4|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|M|8|@$D|N|E|O|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|P|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|K|$]]

All of the other answers have focused on actually testing the code by putting it through its paces and actually running it in one form or another or politely saying "don't do it yourself, use an existing library".

This is great and all, but IMO, the most important (practical tests are important too) test is to look at the code line by line and for every line of code ask "what happens if I get interrupted by another thread here?" Imagine another thread, running just about any of the other lines/functions during this interruption. Do things still stay consistent? When competing for resources, does the other thread[s] block or spin?

This is what we did in school when learning about concurrency and it is a surprisingly effective approach. Bottom line, I feel that taking the time to prove to yourself that things are consistent and work as expected in all states is the first technique you should use when dealing with this stuff.

blocks|key|1815461|text|我通常通过在分布式线程/进程的适当位置插入sleep()调用来测试这类事情。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1815462|例如，要测试一个锁，在争用点将sleep(2)放入所有线程中，并在大约1秒的间隔内产生两个线程。第一个应该获得锁，第二个应该等待。|1815463|大多数竞态条件都可以通过扩展此方法进行测试，但如果您的系统有太多组件，则可能很难或不可能知道需要测试的每个可能的条件。|1815464|entityMap^0|L|7|0|F|8|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@$9|M|A|N|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|O|8|@$9|P|A|Q|B|C]]|D|@]|E|$]]|$1|H|3|I|5|6|7|R|8|@]|D|@]|E|$]]|$1|J|3|-4|5|6|7|S|8|@]|D|@]|E|$]]]|K|$]]

I normally test these kinds of things by interjecting <code>sleep()</code> calls at appropriate places in the distributed threads/processes.

For instance, to test a lock, put <code>sleep(2)</code> in all your threads at the point of contention, and spawn two threads roughly 1 second apart. The first one should obtain the lock, and the second should have to wait for it.

Most race conditions can be tested by extending this method, but if your system has too many components it may be difficult or impossible to know every possible condition that needs to be tested.

blocks|key|2993044|text|并发系统是概率的，错误通常很难复制。因此，您需要运行各种输入/输出用例，每种用例都经过一段时间(小时、天等)的测试，以便检测可能的错误。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2993045|并发数据结构的测试包括检查容器在插入和删除等预期事件之前和之后的状态。|2993046|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

Concurrent systems are probabilistic and errors are often difficult to replicate. Therefore you need to run various input/output cases, each tested over time (hours, days, etc) in order to detect possible errors. 

Tests for concurrent data structure involves examining the container's state before and after expected events such as insert and delete.

blocks|key|1815507|text|如果可能，请使用满足您需求的预先存在的、经过预先测试的库。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1815508|确保代码具有适当的自一致性检查(最好是快速的健全性检查)，并在尽可能多的不同类型的硬件上运行代码，以帮助缩小有趣的计时问题。|1815509|让多个人对代码进行同行评审，最好不要预先解释它是如何工作的。这样，他们必须摸索代码，这应该有助于捕获更多的bug。|1815510|设置一堆只对数据结构执行随机操作的线程，并以一定的速率检查一致性。|1815511|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|L|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|M|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|I|$]]

Use a pre-existing, pre-tested library that meets your needs if possible.

Make sure that the code has appropriate self-consistency checks (preferably fast sanity checks), and run your code on as many different types of hardware as possible to help narrow down interesting timing problems.

Have multiple people peer review the code, preferably without a pre-explanation of how it's supposed to work. That way they have to grok the code which should help catch more bugs.

Set up a bunch of threads that do nothing but random operations on the data structures and check for consistency at some rate.

blocks|key|2993105|text|首先假设访问/修改数据的调用不是线程安全的，并使用锁来确保一次只有一个线程可以访问/修改数据的任何部分。只有在您可以证明多个线程同时在锁外安全地访问特定类型的代码之后，才应该将该代码移到锁外。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2993106|假设出现最坏的情况，例如，您的代码将在某个指针操作或另一个临界点的中间停止，并且另一个线程将在中间转换过程中遇到该数据。如果这会产生不好的结果，就把它留在锁中。|2993107|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

Start with the assumption that your calls to access/modify data are not thread safe and use locks to ensure only a single thread can access/modify any part of the data at a time. Only after you can prove to yourself that a specific type of access is safe outside of the lock by multiple threads at once should you move that code outside of the lock.

Assume worst case scenarios, e.g. that your code will stop right in the middle of some pointer manipulation or another critical point, and that another thread will encounter that data in mid-transition. If that would have a bad result, leave it within the lock.

blocks|key|925694|text|运行你的并发线程一天或几天，看看会发生什么。(听起来很奇怪，但找出竞争条件是一个如此复杂的主题，所以简单地尝试它是最好的方法)。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|925695|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|$]]

Run your concurrent threads for one or a few days and look what happens. (Sounds strange, but finding out race conditions is such a complex topic that simply trying it is the best approach).

What are some methods for testing concurrent data structures to make sure the data structs behave correctly when accessed from multiple threads ?

Testing concurrent data structure

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

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

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

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

文章

问答

视频

教程

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

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

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

腾讯云数据库专区

腾讯云智能顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云AI代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

功能1上新10个字符

功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符。

功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符。

功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符

功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符

功能4上新

文章&问答评论现已支持表情

全新交互，全新视觉，新增快捷键、悬浮工具栏、高亮块等功能并同时优化现有功能，全面提升创作效率和体验

社区富文本编辑器全新改版！诚邀体验～ 

精选全网热门MCP server，让你的AI更好用 🚀

💥开发者 MCP广场重磅上线！

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

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

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

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

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

社区新版编辑器体验调研

有什么方法可以测试并发数据结构，以确保从多线程访问数据结构时数据结构的行为正确？

问测试并发数据结构
EN

回答 6

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问测试并发数据结构EN

回答 6

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问测试并发数据结构
EN