- This topic has 2 replies, 3 voices, and was last updated 14 years, 5 months ago by
.
-
Topic
-
We have currently 3 production sites Site 1
50 threads 250K messages per 24hrs, 3 processes
Site 2
34 threads 100K messages per 24hrs, 2 processes
Site 3
34 threads 200K messages per 24hrs, 2 processes
We are considering consolidate them to a general site with an inbound thread
It will receive all inbound messages that currently going to 3 separate sites now
This site will have
50 threads about 500K messages per 24hrs 3 processes
The question is
Would this large site work slower then 3 separate sites because
all messages will go through one port instead of 3?
Thanks
-
Replies
-
-
I would be less concerned about the speed of the data across the port and more concerned about the fact that you would now be looking at one recovery database, one lock manager, one monitor daemon, etc. Additionally you are consolidating down to 3 processes from 7. That means that you now have 3 translate threads and 3 command threads versus 7. What I know of cloverleaf is that the protocol thread gets the deference in priority over the translate thread which means that translation becomes the weak link in the chain. I can’t promise you that the decrease in translate threads will negatively impact your performance but I would definitely perform some benchmark testing with each of the configurations before I committed to a change like that.
-
-
- The forum ‘Cloverleaf’ is closed to new topics and replies.
