Yes, this is a good idea - we have done this and found it gave a small performance increase.
We also found that while the DemuxingProtocolCodecFactory is useful since it is easy to use, it is worthwhile writing your own custom codec if you are wanting to maximise performance. This is because you can often take advantage of state information so that you "know" which types of frame you are going to receive (or are more likely to receive) rather than going through a list of codecs in a particular order every time.
Robert
| "Trustin Lee" <[EMAIL PROTECTED]>
26/03/2006 15:16
|
To: [email protected] cc: Subject: Removing synchronization on a ProtocolEncoder and a ProtocolDecoder |
Hi,
Peter and I once talked about removing synchronization on a ProtocolEncoder
and a ProtocolDecoder. This synchronization block is a cause of performance
degradation when a user wants to share one encoder/decoder instance between
multiple sessions. I think some decoders and almost all encoders can be
shared safely.
Any idea?
Trustin
--
what we call human nature is actually human habit
--
http://gleamynode.net/
--
PGP key fingerprints:
* E167 E6AF E73A CBCE EE41 4A29 544D DE48 FE95 4E7E
* B693 628E 6047 4F8F CFA4 455E 1C62 A7DC 0255 ECA6
This communication is for informational purposes only. It is not intended
as an offer or solicitation for the purchase or sale of any financial
instrument or as an official confirmation of any transaction. All market prices,
data and other information are not warranted as to completeness or accuracy and
are subject to change without notice. Any comments or statements made herein
do not necessarily reflect those of JPMorgan Chase & Co., its subsidiaries
and affiliates.
