Saturday, November 29, 2014

Digest for comp.lang.c++@googlegroups.com - 3 updates in 1 topic

comp.lang.c++@googlegroups.com Google Groups
Unsure why you received this message? You previously subscribed to digests from this group, but we haven't been sending them for a while. We fixed that, but if you don't want to get these messages, send an email to comp.lang.c+++unsubscribe@googlegroups.com.
woodbrian77@gmail.com: Nov 29 02:27PM -0800

Currently all messages between my back and middle tiers
are compressed. The following shows the messages the
middle tier sends to the back tier.
 
middle_messages_back
@out (messageid_t, ::std::vector<cmw_account_info>)
@out (messageid_t, ::cmw::marshalling_integer, cui_generator)
@out (messageid_t)
}
 
The first message there is a login request. The second
is a code generation request and the last is a keep alive.
The keep alive is just a messageid_t which, in this case,
is one byte. After being compressed, the keep alive
message increases to 12 bytes. I think compression is
helpful for the code generation request message, but not
for the keep alive message. I'd guess compression isn't
helping with the login message either, but am not sure.
I've worked on systems that use compression for
everything or not at all. Have you ever worked on a
system that uses both compressed and non-compressed
messages? I'd like to find some info on systems like that.
 
Brian
Ebenezer Enterprises - In G-d we trust.
http://webEbenezer.net
Mr Flibble <flibbleREMOVETHISBIT@i42.co.uk>: Nov 29 10:59PM

> everything or not at all. Have you ever worked on a
> system that uses both compressed and non-compressed
> messages? I'd like to find some info on systems like that.
 
Sausages.
 
/Flibble
Ian Collins <ian-news@hotmail.com>: Nov 30 12:10PM +1300

> everything or not at all. Have you ever worked on a
> system that uses both compressed and non-compressed
> messages? I'd like to find some info on systems like that.
 
Compression is seldom any use for anything other than bulk transfer of
compressible data or sausages.
 
For inter-process or intra-process messages the overheads incurred by
compression tend to outweigh any benefits for short messages and for
LAN/WAN messaging packet latency has much more of a performance impact
than packet size.
 
One example is the application I use to distribute filesystems between
local and geographically distributed hosts, there I only consider
compression for full (not incremental) transfers of filesystems with a
worthwhile compress ratio.
 
--
Ian Collins
You received this digest because you're subscribed to updates for this group. You can change your settings on the group membership page.
To unsubscribe from this group and stop receiving emails from it send an email to comp.lang.c+++unsubscribe@googlegroups.com.

No comments: