in reply to Max no of Threads

What would be the ideal no of threads that i should be run at once ?
23*
Should i go for forking multiple process instead ?

Threads do have problems, but they also have their use. When the processes don't need to exchange data, processes might be more stable and easier to handle. Might.

(*: How do you think we can tell you what's best for your use case if we don't know your use case?)

Replies are listed 'Best First'.
Re^2: Max no of Threads
by zentara (Cardinal) on Aug 22, 2008 at 13:14 UTC
Re^2: Max no of Threads
by libvenus (Sexton) on Aug 22, 2008 at 08:22 UTC

    Well the case is in a differnet thread "Problem in Inter Process Communication "

      Or as a link: Problem in Inter Process Communication. (See What shortcuts can I use for linking to other information?)

      I skimmed over the first few posts in that thread, and I still don't know what your application actually does (or should do).

      The best number of threads/processes strongly depends on the nature of your computations. For example if it's mostly CPU bound, it pays off to have exactly one worker thread/process per CPU core. For a web server that's often a very bad choice.

      So tell us what kind of problem your application tries to solve. Otherwise we can't give any advice on what's "best" for you.

        Hi moritz,

        Here is a description of the app:-

        Well i have been assigned a task to migrate a regression suite from c++ to perl. The reg suite has a task to fire queries to prod and test and then compare the results.The queries are fired to a few app servers. The no of client which must be replaced in each query is around 10K and the no of queries is around 5K.The result of the query fired can contain 10 K records at times.Firing query generally takes much less time than comparison and this is the primay reason y i want to segregate things this way. Each query must be replaced by all the clients and then fired onto the app servers

        Thanks