|
Re: [CDO-Net4j] Compression of Net4j/CDO streams [message #991825 is a reply to message #991500] |
Thu, 20 December 2012 09:28 |
|
Am 19.12.2012 15:43, schrieb Guido Scalise:
> Hi!
> is it possible to add compression to the Net4j TCP connector? We are trying to work with a repository, accessing it
> over a 20Mbit and 50Mbit VPNs and the performance is not as good as we expected.
> We've tweaked the view prefetch options and the session collection retrieval policy and the performance improved a
> bit, but we'd like to gain more performance, and being able to compress the Net4j stream seems like the next logical
> step.
>
> Eike, do you see any drawbacks on this? I was thinking of a *very* lightweight stream compressor so as not to
> overload the server CPU with (CPU intensive) stream compression tasks, but maybe you've already implemented this in
> some way.
You can add IStreamWrappers to the protocol instances that are created per CDOSession:
org.eclipse.net4j.signal.ISignalProtocol.setStreamWrapper(IStreamWrapper)
org.eclipse.net4j.signal.ISignalProtocol.addStreamWrapper(IStreamWrapper)
A simple example is in SignalStreamWrappingTest.
These components are IContainers that emit IContainerEvents when new elements are added:
IAcceptor
IConnector
IConnectors (both on client and server side) have IChannels and an IChannel has an ISignalProtocol
Let me know if you need more hints ;-)
Cheers
/Eike
----
http://www.esc-net.de
http://thegordian.blogspot.com
http://twitter.com/eikestepper
Cheers
/Eike
----
http://www.esc-net.de
http://thegordian.blogspot.com
http://twitter.com/eikestepper
|
|
|
Powered by
FUDForum. Page generated in 0.02065 seconds