exchange used: fanout we are running broker on 2 core machine. fanout send client is also running on the same windows machine. there are 3 recv applications running on three separate machines.
we were trying with-> --worker-thread 9 which gives poor performance compared to without --worker-threads option now we have taken --worker-threads 2 as no of processors on the machine where broker is running is 2. in this case how many threads exactly has to be used to so as to improve performance Thanks Gordon Sim wrote: > > ft420 wrote: >> hi, >> >> without --worker-thread option pidstat command shows that there are by >> default 6 threads created >> with --worker-thread 6 option pidstat command shows that there are 9 i.e. >> default 6 + 3 threads created. > > Fyi: the extra three threads are timer threads for various different > tasks. > >> As per documentation worker threads option is used to improve >> performance. >> I checked with --worker-thread 10 and without --worker-thread. >> direct_producer sends 100000 messages put time increases with >> --worker-thread 10 as compared to --worler-thread option. > > Running more threads than there are processors will not improve any real > parallelism. There is also no real value from using more threads than > you have active connections (so in a test with just one producer and one > consumer connection you won't see any benefit from having more than 2 > worker threads). > > --------------------------------------------------------------------- > Apache Qpid - AMQP Messaging Implementation > Project: http://qpid.apache.org > Use/Interact: mailto:[email protected] > > > -- View this message in context: http://n2.nabble.com/worker-thread-with-qpidd-tp3016587p3017154.html Sent from the Apache Qpid users mailing list archive at Nabble.com. --------------------------------------------------------------------- Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:[email protected]
