When should I use multi threading in applications i make?
When should I use multi threading in applications i make?
Parker Cruz
Adrian Brooks
>When should I use multi threading in applications i make?
Why?
Joshua Foster
because i have application that go trough lot of data.
Isaac Gonzalez
when your application has stuff that should appear to be running on parallel
Ian Cox
>When should I use multi threading in applications i make?
when it makes sense to.
>because i have application that go trough lot of data.
if the threads don't need to share data, then sure go for it. can't have data races that way.
Cooper Parker
ペロペロしたい
Easton Ross
When you have multiple jobs done in parallel. When you have to read a bunch of shit, but you don't have to write.
Jayden Foster
why are anime girls so cute...
Kevin Ward
Why aren't you? I'm cute as hell, my nigga. I am a beautiful man with smooth skin and big nuts. I draw anime faces on my nuts so that when a bitch is sucking on them it looks like she's having a threesome with anime bitches.
Lucas Torres
Aaron Cooper
i bet that she has lots of good milk
Ethan Long
needs corrective rape 💢
Joshua Baker
...
Nathaniel Thompson
its astounding, faggots are still posting my shitty edit in Year of Our Lord 2022
look around the tits, look at the doorknob
Mason Evans
people only see the tits :D
Henry Allen
itoddlers will never recover from this 🙄
Adrian Perry
Whenever you have things you want to do concurrently and don't want to block on, I guess.
I don't usually bother, though.
Colton Howard
I hate that the artist draws her face so well but gives her cow tits
Nathaniel Nelson
you always need an UI thread and a background thread. then from your background thread you have to start more tasks, threads that get closed after processing
Elijah Campbell
>When should I use multi threading in applications i make?
When there are things that can be done in parallel, and it makes sense to go through the trouble of parallelization.
Parallelism is more than just concurrency. Async/await and similar modes of starting a task then waiting to resume are concurrent, but aren't necessarily parallel. There's very rarely a reason not to use concurrency when it's available, but parallelism requires careful consideration to avoid data races and race conditions.
Jeremiah Price
...
Aiden Russell
>make thread with low-effort question
>post anime porn as OP image
>OMG POST MOAR OF HER
Is it a discord spamming these?
Levi Miller
how do i get a female gf bros...
Chase Jackson
When you need two sets of computations done in parallel. If you just have IO operations (reading from file/network etc) that need to work in parallel then you are better off using asynchronous approaches.
In general though you should avoid just creating a bunch of threads and dealing with the problems that can cause. Try to use a correct abstraction for what you want to do. For example, usually a job queue with a threadpool backing it is a good approach and most languages will have a decent library for this.