# Interrupt \`Threads.@threads\` computation

**URL:** <https://discourse.julialang.org/t/interrupt-threads-threads-computation/71199>\
**Category:** General Usage\
**Tags:** multithreading, task, threads\
**Created:** [November 9, 2021, 10:27am UTC](https://discourse.julialang.org/t/interrupt-threads-threads-computation/71199 "2021-11-09T10:27:08Z")\
**Posts on this page:** 1\
**Showing post:** 7

<div class="post-metadata">

**Author:** ![Marcell\_Havlik](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/marcell_havlik/32/37424_2.png) [@Marcell\_Havlik](https://discourse.julialang.org/u/Marcell_Havlik)\
**Post date:** [April 24, 2023, 6:15am UTC](https://discourse.julialang.org/t/interrupt-threads-threads-computation/71199/7 "2023-04-24T06:15:48Z")

</div>

You can make it atomic if you don’t want to do any more computation or avoid any dirty read.  
For me it doesn’t matter if there is 4-30 more computation with dirty read on `stop_cond` as I am just interrupting the next 10 million computation which is the key. Also we mustn’t forget that the computations are whole so the results from each dirty read case is valid and are saved in the `trials_db`, so I can already work with ready computations perfectly.

---

_[View the full topic](https://discourse.julialang.org/t/interrupt-threads-threads-computation/71199)._