Print

Print


Hi,

currently a multithreaded slave waits until the complete eval.masterproblem.job-size (the master "offers") is processed.

Can this behaviour be changed to something where multithreaded slave processes individuals as soon as possible e.g., if the job-queue is still filled? 
 
AFAIK the motivation for the current approach is the reduce the required network bandwidth between master/slaves. My motivation is to reduce the memory consumption of each slave (because of a large DB each slave need to "carry").

Greetings,

	Ralf