- This topic has 2 replies, 2 voices, and was last updated 14 years, 7 months ago by
.
-
Topic
-
Hi, Here is the situation I have:
ThreadA -> ThreadB ->ThreadC
ThreadA calls a webservice on a timer and gets a HL7 message. ThreadA takes the single HL7 message and xlates it and will split it up in to several different messages using the CONTINUE Action to forward each message to ThreadB.
ThreadB receives these messages, does some logging and then sorts the OBR and OBX segments using a Tcl proc in the TPS Outbound Data section. Then using the OVER disposition it puts the message to another xlate which does a basic translation and then forwards to ThreadC.
My questions are:
1.
-
Replies
-
-
A Cloverleaf process allocates some time to each thread within the process, including the Xlate thread. If all of these threads are in the same process, what you may be seeing is ThreadA processing, the Xlate thread processsing, the ThreadB processing, etc. If you want more CPU thrown at this, you may want to consider splitting this up into two processes, so the Xlate threads are split up between them. This should help with your processing and throughput.
One warning, there is a cost for inter-thread communication, and only testing with large batches will show you which is better. My gut feeling is that having two processes, each asking for CPU time (vs. one) will outperform the cost of the inter-thread communication.
Hope this helps,
Robert Milfajt
Northwestern Medicine
Chicago, IL -
-
- The forum ‘Cloverleaf’ is closed to new topics and replies.
