--- title: Multithreading for Beginners | daily.dev description: Multithreading allows concurrent execution of threads for optimized resource use and improved application performance. It is crucial for handling multiple... canonical: https://daily.dev/posts/multithreading-for-beginners-f34zd0p4j twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: Multithreading for Beginners | daily.dev og:description: Multithreading allows concurrent execution of threads for optimized resource use and improved application performance. It is crucial for handling multiple... og:url: https://daily.dev/posts/multithreading-for-beginners-f34zd0p4j og:image: https://api.daily.dev/og/posts/f34ZD0P4j.png og:image:alt: Multithreading for Beginners og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # Multithreading for Beginners **[freeCodeCamp](https://daily.dev/sources/freecodecamp)** · 3 min read · 522 upvotes · 5 comments ## Summary Multithreading allows concurrent execution of threads for optimized resource use and improved application performance. It is crucial for handling multiple tasks simultaneously and is extensively used in Java. A comprehensive course on the freeCodeCamp.org YouTube channel covers multithreading basics to advanced topics, including thread creation, synchronization, inter-thread communication, and advanced frameworks like ExecutorService and ForkJoinPool. The course aims to enhance programming skills and opens up numerous career opportunities. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Community discussion Top comments from developers on daily.dev. **@riskvrocks** · 2 upvotes > 4. NEVER assume that the code you write is thread-safe. You need to stress test it with thousands of threads. You do not know how the assembler code is generated, where the thread will jump in. > I learned this way when my thread crashed on an int assignment (Delphi). "int temp = 12545" seems like an atomic operation, the CPU will not jump to another thread, but it did in the middle of the Delphi instruction. Only when you looked at the assembler code did you realize that the compiler made it into 2 assembler instructions. And the thread jumped after the first assembler instruction. **@riskvrocks** · 2 upvotes > 5 hours is too long for me to go through, but I will give some hints I learned from working with enormous numbers of threads. > > 1. I mark each method like this {rwRW} {r-r-}{rw--}. > r/R = read safe > w/W = write safe > rw = read/write safe during initialization phase > RW = read/write safe in full run mode. > > Most of the time you will probably use {rwRW} or {--RW}. > > When no threads are running (initialization phase), you can set global variables and no locking is required. Once they are running, they are only read, never written, so locking is not required. **@riskvrocks** · 1 upvotes > 2. (I don't know in Jave but in C) Create your data so that it fits into a struct, you just have to memcopy that struct (fast and never gets an error), and that's the only time you need to lock a part. When you work on that copied structure, you don't need to lock any properties anymore. All data stays in sync, no property in this struct will be changed by any other thread. **@riskvrocks** · 1 upvotes > 3. People always claim that lock() is always slow. I have heard this claim for decades, but it is not true. It is ONLY slow when there is a collision, but it takes micro/nanoseconds to lock() when there is no collision. > > The key here is to make the lock as short as possible. This is why I refer to using memcopy to copy a struct with your data in it and lock only during the memcopy. We are talking about microseconds here. > > You lose a bit of memory because you allocate more local memory for your thread to work on. But you don't lose any speed because the chance of getting into a collision is... ## Similar posts on daily.dev - [Don’t just attend KubeCon \+ CloudNativeCon, Merge Forward your experience\!](https://daily.dev/posts/don-t-just-attend-kubecon-cloudnativecon-merge-forward-your-experience--l0rpp73x8) · CNCF · 1 upvotes · 0 comments - [Announcing H2 2026 KCDs](https://daily.dev/posts/announcing-h2-2026-kcds-m96goajm1) · CNCF · 1 upvotes · 0 comments - [Two months of Open Community Groups](https://daily.dev/posts/two-months-of-open-community-groups-asf52zhbs) · CNCF · 0 upvotes · 0 comments - [CNCF Unveils Schedule for KubeCon \+ CloudNativeCon Europe 2026](https://daily.dev/posts/cncf-unveils-schedule-for-kubecon-cloudnativecon-europe-2026-ikhcoa5cb) · CNCF · 2 upvotes · 0 comments - [CNCF Debuts KubeCon \+ CloudNativeCon Japan 2026 Schedule](https://daily.dev/posts/cncf-debuts-kubecon-cloudnativecon-japan-2026-schedule-xp5pyudub) · CNCF · 1 upvotes · 0 comments --- Tags: [#java](https://daily.dev/tags/java) [View this post on daily.dev](https://daily.dev/posts/multithreading-for-beginners-f34zd0p4j) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"Multithreading for Beginners","url":"https://daily.dev/posts/multithreading-for-beginners-f34zd0p4j","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/multithreading-for-beginners-f34zd0p4j"},"datePublished":"2024-07-16T22:35:54.470Z","dateModified":"2024-08-23T16:02:46.896Z","description":"Multithreading allows concurrent execution of threads for optimized resource use and improved application performance. It is crucial for handling multiple...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/ca70cc51a15f64c2b7270fd61f840179?_a=AQAEuiZ","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/ca70cc51a15f64c2b7270fd61f840179?_a=AQAEuiZ","isAccessibleForFree":true,"articleSection":"freeCodeCamp","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"freeCodeCamp","logo":"https://media.daily.dev/image/upload/t_logo,f_auto/v1628412854/logos/freecodecamp","url":"https://daily.dev/sources/freecodecamp"},"commentCount":5,"discussionUrl":"https://daily.dev/posts/multithreading-for-beginners-f34zd0p4j","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":522},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":5}],"keywords":"java","timeRequired":"PT3M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"freeCodeCamp","item":"https://daily.dev/sources/freecodecamp"},{"@type":"ListItem","position":3,"name":"Multithreading for Beginners"}]} {"@context":"https://schema.org","@type":"WebPage","@id":"https://daily.dev/posts/multithreading-for-beginners-f34zd0p4j","comment":[{"@type":"Comment","text":"NEVER assume that the code you write is thread-safe. You need to stress test it with thousands of threads. You do not know how the assembler code is generated, where the thread will jump in.\nI learned this way when my thread crashed on an int assignment (Delphi). “int temp = 12545” seems like an atomic operation, the CPU will not jump to another thread, but it did in the middle of the Delphi instruction. Only when you looked at the assembler code did you realize that the compiler made it into 2 assembler instructions. And the thread jumped after the first assembler instruction.","datePublished":"2024-09-15T09:54:41.123Z","url":"https://daily.dev/posts/f34ZD0P4j#c-ZMyBEAg1r","author":{"@type":"Person","name":"Olaf Baeyens","url":"https://daily.dev/riskvrocks","image":"https://lh3.googleusercontent.com/a/ACg8ocLJkJY8ilgA58cB98-bqw06GH4y8U6Fr2WpPHbHKTH2c3Ru3w=s96-c"},"interactionStatistic":{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":2}},{"@type":"Comment","text":"5 hours is too long for me to go through, but I will give some hints I learned from working with enormous numbers of threads.\n\nI mark each method like this {rwRW} {r-r-}{rw–}.\nr/R = read safe\nw/W = write safe\nrw = read/write safe during initialization phase\nRW = read/write safe in full run mode.\n\nMost of the time you will probably use {rwRW} or {–RW}.\nWhen no threads are running (initialization phase), you can set global variables and no locking is required. Once they are running, they are only read, never written, so locking is not required.","datePublished":"2024-09-15T09:35:43.354Z","url":"https://daily.dev/posts/f34ZD0P4j#c-JHgTS1npn","author":{"@type":"Person","name":"Olaf Baeyens","url":"https://daily.dev/riskvrocks","image":"https://lh3.googleusercontent.com/a/ACg8ocLJkJY8ilgA58cB98-bqw06GH4y8U6Fr2WpPHbHKTH2c3Ru3w=s96-c"},"interactionStatistic":{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":2}},{"@type":"Comment","text":"(I don’t know in Jave but in C) Create your data so that it fits into a struct, you just have to memcopy that struct (fast and never gets an error), and that’s the only time you need to lock a part. When you work on that copied structure, you don’t need to lock any properties anymore. All data stays in sync, no property in this struct will be changed by any other thread.","datePublished":"2024-09-15T09:40:11.151Z","url":"https://daily.dev/posts/f34ZD0P4j#c-ZBWLsHFfu","author":{"@type":"Person","name":"Olaf Baeyens","url":"https://daily.dev/riskvrocks","image":"https://lh3.googleusercontent.com/a/ACg8ocLJkJY8ilgA58cB98-bqw06GH4y8U6Fr2WpPHbHKTH2c3Ru3w=s96-c"},"interactionStatistic":{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":1}},{"@type":"Comment","text":"People always claim that lock() is always slow. I have heard this claim for decades, but it is not true. It is ONLY slow when there is a collision, but it takes micro/nanoseconds to lock() when there is no collision.\n\nThe key here is to make the lock as short as possible. This is why I refer to using memcopy to copy a struct with your data in it and lock only during the memcopy. We are talking about microseconds here.\nYou lose a bit of memory because you allocate more local memory for your thread to work on. But you don’t lose any speed because the chance of getting into a collision is very small.","datePublished":"2024-09-15T09:48:20.005Z","url":"https://daily.dev/posts/f34ZD0P4j#c-i7L6n8XG2","author":{"@type":"Person","name":"Olaf Baeyens","url":"https://daily.dev/riskvrocks","image":"https://lh3.googleusercontent.com/a/ACg8ocLJkJY8ilgA58cB98-bqw06GH4y8U6Fr2WpPHbHKTH2c3Ru3w=s96-c"},"interactionStatistic":{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":1}}]} ```