Thread: Multithreading

It can, yes - additionally, it depends on what your function's doing. If it's making some system call that might block, it will be much more efficient to make it ten times concurrently than it will be to make it ten times consecutively. If the call is for blocking I/O, for example, where most of the time will be spent waiting for hardware to do whatever it's doing, this may well be the case.

Originally Posted by Sipher

Ok, but can i say that those 10 thread, or some of them, run at exactly the same time?

Up to two of them may do, on a dual-core processor, but that would be an accident and not generally something you'd care to know about. They only run "at the same time" in a conceptual sense - it's a useful way to think about them at a certain level of abstraction (e.g. when you want to make ten system calls concurrently), but in actual fact they probably won't literally run at the same time.

This may be a stupid question, but it has happened to me: Are you sure the function is thread safe? If it's not, the concurrency could mess it up, causing some threads' execution of the function to prematurely return.