I came across QtConcurrent and QFutureWatcher only after I started down this path, and I was rather hoping to see if I can figure out why this isn't working before completely abandoning in favour of that approach. Realistically I can see situations where both approaches would be useful, and I would like to have both as viable options.

@SGaist yes, thx, my fault was trying to iterate through the future until not be ready.
now i got what i want, not as fast as i want, but it works stable.

Hi,

You can connect the "finished()" signal to a slot and there check if all threads are not running. I assume that you have a list of threads.

@Cocojambo said in Load balancing between several Threads:

I mean that all 4 new threads may be created in one core and we won't get any benefit of such multi threading.

You can't with Qt. But the OS will for sure not put all four threads on one core and leave the other three idle when the four have something to do.

Looks like you are re-implementing tools that already exist for that purpose. Was tmux/xpanes considered ?

In any case, before doing any threading, you should have a proper encapsulation for your connection and command sending. Once you have that you can start thinking about threads or maybe use QtConcurrent. It looks like you rather have lists of commands to send to machines. A bit like what ansible manages for you with its playbook.

@VRonin said in Need Help with getting a slot executed in the correct thread:

the default implementation of QThread::run starts an event loop so if you use the method described in that link everything will work out of the box

Indeed it does! Thanks!

Like I already wrote, it has nothing to do with Qt. Qt is a C++ framework, it doesn't do anything special with respect to memory management.

So yes, since the OP wrote that the memory was not freed after the application ended then he needs to elaborate on that.

@kshegunov thank you very much really appreciate you taking your time to explain all this to me. And your are right. as soon as i connected both disconnect signals to the deleteLater() and went down the signals and slots road all the problems vanished. Thank you really. Because i had alot of time to spare i also followed @herlarbee suggestion(even though i watched this videos already) then decided to write a seperate server using QThreadPool approach seen on in the video title "Qt TCP Server design revisited". Then i benchmarked both. This new server after doing some benchmark test using ab tool in apache seems to outperform my previous solutions and handles alot more connections faster. Right now am very happy. When asking this question i just had 200 client limit in my brain but i got solutions that go way beyond that. Thank you guys.

Cheers !!!

I'm using this code on the server. By blocking I simply meant that if one client requested something that took long to process it shouldn't block the other clients. I may upload a working sample of this code to github later.