Re^3: ithreads or fork() what you recommend?

pawan68923,

...only thing they need to share (read and write both) using file is - how many processes of one type are in execution...

I would have the the parent keep these counters in memory. From your description the parent starts the processes and maintain the counts. Why use a file?

Some things to consider:

Test your theory. That many CPUs may act different than you (or I) might think. I have many times assumed a solution to find that it didn't scale well. You could have dependencies that you don't even know exist.
Always lock even it's "read only". 'flock' is trivial compared to the time fixing a solution that now will "read and write" only one thing.

Sounds like a massive undertaking -- should be fun!

Good Luck!

"Well done is better than well said." - Benjamin Franklin

Comment on Re^3: ithreads or fork() what you recommend?

Replies are listed 'Best First'.
Re^4: ithreads or fork() what you recommend? by Anonymous Monk on May 19, 2012 at 16:35 UTC
Hi Flexvault, Its my mistake when I mentioned use of file to count child process state, actually I used parent's counter in memory to do that in the test code I wrote as skeleton of the modified solution. I will make use of your advise. Thanks much! Best regards, Pawan#	[reply]