You are not logged in. Your edit will be placed in a queue until it is peer reviewed.
We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.
- 1Before you try to understand the full program, make sure you understand the threads and how they interact, the synchronisation and the touchpoints between them. Once you have that skeleton, you can try to analyze each thread in what it's doing just like a separate program. That won't make the process much easier, but at least more structured.tofro– tofro2016-09-29 10:42:28 +00:00Commented Sep 29, 2016 at 10:42
- 16Proponents of alternative approaches to concurrency and parallelism (e.g. STM, Actors, Dataflow) would probably say that if you feel that multithreading with shared mutable state and locks is a horrible complicated mess that makes your head explode and cannot be properly understood, then you have, in fact, fully understood multihreading with shared mutable state and locks ;-)Jörg W Mittag– Jörg W Mittag2016-09-29 16:35:47 +00:00Commented Sep 29, 2016 at 16:35
- Piggy-backing on Jörg's comment, allow me to direct your attention towards an essay called On structured concurrency, Or: Go statement considered harmful and the various talks and blog posts by Ron Pressler about Project Loom. They agree with your assessment that concurrency as it is right now is too complicated for humans brains, similar to how programs with copious amounts of goto statements are too complicated, and they propose "structured concurrency" as a way out.Johannes Hahn– Johannes Hahn2020-11-04 11:22:49 +00:00Commented Nov 4, 2020 at 11:22
- I'll add to write small programs to try to replicate the unexpected behavior. Try to create a race condition, see it happening, then try different approaches to solve it. You learn a lot about concurrency when you catch, find and solve bugs, but on a production environment the bugs are harder to happen and find.Marcos Vinícius da Silva– Marcos Vinícius da Silva2020-11-04 23:28:02 +00:00Commented Nov 4, 2020 at 23:28
Add a comment |
How to Edit
- Correct minor typos or mistakes
- Clarify meaning without changing it
- Add related resources or links
- Always respect the author’s intent
- Don’t use edits to reply to the author
How to Format
- create code fences with backticks ` or tildes ~ ```
like so
``` - add language identifier to highlight code ```python
def function(foo):
print(foo)
``` - put returns between paragraphs
- for linebreak add 2 spaces at end
- _italic_ or **bold**
- indent code by 4 spaces
- backtick escapes
`like _so_` - quote by placing > at start of line
- to make links (use https whenever possible) <https://example.com>[example](https://example.com)<a href="https://example.com">example</a>
How to Tag
A tag is a keyword or label that categorizes your question with other, similar questions. Choose one or more (up to 5) tags that will help answerers to find and interpret your question.
- complete the sentence: my question is about...
- use tags that describe things or concepts that are essential, not incidental to your question
- favor using existing popular tags
- read the descriptions that appear below the tag
If your question is primarily about a topic for which you can't find a tag:
- combine multiple words into single-words with hyphens (e.g. design-patterns), up to a maximum of 35 characters
- creating new tags is a privilege; if you can't yet create a tag you need, then post this question without it, then ask the community to create it for you
lang-java