Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[stoatwblr]

Currently compression is forced on between client and server at all times.(*)

Server/client compression is always a tradeoff between consumption of available CPU resource and throughput gains.

For any given system: Beyond a threshold link speed/latency, throughput becomes hard-limited by compression engine throughput ability, not the network speed. At this point compression becomes a net loss and should be disabled.

For amule(d) - amulegui interactions this basically means that compression is getting in the way for Loopback and LAN connections and may well be a loss for faster WAN connections too.

Disabling client/server compression will have the greatest noticeable effect on low power desktops and setups such as routers, embedded systems or low power fileservers  running amuled that are accessed via a local network desktop.

(*) Amule(d) and the amuleweb client already have switchable compression on client/server interactions, so hopefully it's just a matter of reusing the same code for other Amule clents.

[skolnick]

IMO, amule's compression engine is very efficient and it should not be disabled. It always saves bandwidth, since on any recent machine (Pentium III onwards) compression engine throughput is faster than WAN links (I tested aMule with two clients on a single LAN and it threw like 20-25Mbps), so the option to disable it seems silly to me. Also, the compression on the amuleweb is just for the HTTP traffic from the web client to amuleweb, it has nothing to do with aMule's traffic compression. I have never used amuled, so I can't comment for sure on it, but I bet it's a similar option.

Regards.

[lfroen]

This is not an issue. In amuled <-> amuleweb communication compression turned on only for packets of > 1K IIRC. Majority of packets is smaller, thus no compression.
HTTP compression is good thing, since often access to amuleweb made over slow links, and html pages can be quite big.

[Kry]

I think he means client<->client, on ED2K.

[stoatwblr]

I mean between amule/amuled (server) and amulegui/amulecmd (client)


This has nothing to do with p-p, kad, ed2k or http traffic.

[Kry]

Oh I see. Then lfroen's applies.