Multithread - multiprocess application clarification
<br>
I was working with scalability issues of an legacy application, and come to know that this application uses multi-process ( may be equivalent to no. of cores to make it parallelize ) and multi-threaded ( N threads per process, to make it concurrent ). The reason behind the approach doesn't seems to be cleared to me. Though they say that it is because of might be following reasons :- <br>
1) Making too many threads in the single process, doesn't scales well ( lets say 100 threads on one process with 100 core system), some-what kills the parallelism. Does this happens really ?
2) If at some point one thread kills/terminate then it kill the whole process too. I agree with this, but does this also happen frequently ( like chrome is built on multi-process model )
<br><br>
Have any one experienced this kind of behaviour from your application, please let me know what are the appropriate reason behind this theory. Because sharing objects between the processes is also hard ( time consuming ) than sharing between threads.
also apache is using multi-threaded, multi-process server ( little knowledge , please correct if know ).<br>
Or what can be the advantage of using such design for future many core system ?


Multithread - multiprocess application clarification
===

<br>
I was working with scalability issues of an legacy application, and come to know that this application uses multi-process ( may be equivalent to no. of cores to make it parallelize ) and multi-threaded ( N threads per process, to make it concurrent ). The reason behind the approach doesn't seems to be cleared to me. Though they say that it is because of might be following reasons :- <br>
1) Making too many threads in the single process, doesn't scales well ( lets say 100 threads on one process with 100 core system), some-what kills the parallelism. Does this happens really ?
2) If at some point one thread kills/terminate then it kill the whole process too. I agree with this, but does this also happen frequently ( like chrome is built on multi-process model )
<br><br>
Have any one experienced this kind of behaviour from your application, please let me know what are the appropriate reason behind this theory. Because sharing objects between the processes is also hard ( time consuming ) than sharing between threads.
also apache is using multi-threaded, multi-process server ( little knowledge , please correct if know ).<br>
Or what can be the advantage of using such design for future many core system ?

