search

eclipse-ee4j / glassfish-shoal

Shoal
Other
5 stars 9 forks source link

Improved concurrency for sendMessage #89

Open glassfishrobot opened 15 years ago

glassfishrobot commented 15 years ago

RFE related to fix for shoal issue 88 to change that synchronization solution to a more performant pool of OutputPipes (one pipe to be used by one thread at any point in time).

Environment

Operating System: All Platform: All

Affected Versions

[current]

glassfishrobot commented 6 years ago
glassfishrobot commented 15 years ago

@glassfishrobot Commented Reported by @jfialli

glassfishrobot commented 12 years ago

@glassfishrobot Commented shreedhar_ganapathy said: Transferring to Joe for eval and closure.

glassfishrobot commented 12 years ago

@glassfishrobot Commented @jfialli said: there are trade offs for concurrent sendMessage when relying on NIO as the ultimate transport. so this RFE was considered and postponed due to these tradeoffs.

The concurrent processing resulted in not being able to share the same deserialized output stream with all send messages. Thus, there is also a space usage and/or multiple desserializations necessary for each concurrent send.

With regular multicast, only one deserialization of the message to be sent was occurring. With current implementation, there still is only one.

With concurrent send, there were not so obvious tradeoffs. So this RFE is on hold for now while sorting through the tradeoffs.

glassfishrobot commented 7 years ago

@glassfishrobot Commented This issue was imported from java.net JIRA SHOAL-89