Too many threads?

This topic has 8 replies, 6 voices, and was last updated 18 years, 4 months ago by Jared Miller.

Creator

Topic
August 14, 2006 at 1:37 pm #48702
Clay Pendleton
Participant
Good Morning! I have a situation here…

I have one process that handles all ADT threads. I currently have 18 outbound threads. These days, EVERYONE wants ADT, and I have 4 more that need to be added. I fear that I may be putting too much stress on that one process. Any recommendations on how to balance the load?

Running 3.8.0

Thanks, Clay
Creator

Topic

Viewing 7 reply threads

Author

Replies
- August 14, 2006 at 11:10 pm #59431
  Anonymous
  Participant
  Break the threads into multiple processes. With a tcp/ip thread from the source process to the second processes. We are currently doing this we have 5 processes each with at least 9 threads in them. This has saved us a lot of grief.
- August 15, 2006 at 2:00 am #59432
  Dennis Pfeifer
  Participant
  Note to Charlie:…
  
  This would be a good topic for UG ..
  
  Various site designs. Advantages, and disadvantages of each design.
  
  When to split to multiple sites .. i.e. when does the IE local database locking become a problem .. how to determine that you have a problem?
  
  When is too many processes a problem?
  
  Topics in this vain .. general site designs from the different facilities you have worked with, and some of the problems they have had, and how they were resolved….
  
  Thanks
  
  Dennis
- August 15, 2006 at 12:08 pm #59433
  Charlie Bursell
  Participant
  Sorry Dennis, the topics have been set for sometime now.
  
  This is a *very* broad topic with so many permutations. I think, rather than trying to come up with generalized sokutions, this is something you can discuss during the Implementer one-on-one meetings. An Implementer can then address your specific needs.
  
  There is no “one size fits all” here. Some may have to add an additional site at 40 threads, while others may be OK at 90 threads.
- August 15, 2006 at 12:16 pm #59434
  Dennis Pfeifer
  Participant
  I have no specific need .. jus thought it would be of general interest to users…
  
  Dennis
- August 15, 2006 at 12:30 pm #59435
  Jim Kosloskey
  Participant
  Dennis,
  
  We could have an informal gahering of interested users (a Birds Of Feather – BOF if you will) and simply discuss what many of us have experienced and done.
  
  Jim Kosloskey
  
  email: jim.kosloskey@jim-kosloskey.com 29+ years Cloverleaf, 59 years IT - old fart.
- August 15, 2006 at 3:17 pm #59436
  Clay Pendleton
  Participant
  That’s going to be a lot of work, but I’ll give it a shot.
  
  Thanks for the response!
- August 17, 2006 at 7:14 pm #59437
  Clay Pendleton
  Participant
  John,
  
  I built a new thread and added it to a new process. I can’t seem to get it to go into ‘up’ status. I tried protocols tcp/ip and pdl-tcp/ip (I’m not sure what the difference is).
  
  Question: How do I get the engine to send HL7 to itself?
  
  I have the original inbound ADT thread (adt_in) in process adt1. I created the new thread (adt2_in) and process adt2. I’m trying to get adt_in to send raw HL7 to adt2_in. I plan to move some of the outbound threads to receive from adt2_in, but it stays in ‘opening’. When I push a message through using SMAT, it goes to all my other outbound threads, but not to adt2_in.
  
  Am I doing this correctly? Any advice is appreciated.
- August 18, 2006 at 5:24 pm #59438
  Jared Miller
  Participant
  Use TCP/IP…on your outbound thread, set the type to client w/ the Host as localhost, then choose a port…on your inbound thread, set the type as server and use the same port. when you start them both they should connect fine. I use this for going from process to process and from site to site.
Author

Replies

Viewing 7 reply threads

The forum ‘Cloverleaf’ is closed to new topics and replies.