Free Allegiance Forums

Hey devs,

I don't know the current state on compression built into AU but I was thinking if LZMA(2) is too resource heavy you could try out LZO or even GZip.

LZO should only really produce benefits.


EDIT:
For those not aware Imago had included it a while back . . . it's a good idea rally.

Hmm no comments? LZO compression is very very fast, though it doesn't have as good of a ratio as gzip (but the ratio isn't as huge of a concern). I don't know how well older computers handle it.

Keep in mind it's not just to save server bandwidth, but client bandwidth.

Most of the heavy data being transferred over AU are images, I would think... and compression on images is usually a nonstarter, as they're binary data and often already compressed, where most compression algorithms work best on textual data.

Orion wrote:QUOTE (Orion @ Feb 18 2012, 02:20 PM) Most of the heavy data being transferred over AU are images, I would think... and compression on images is usually a nonstarter, as they're binary data and often already compressed, where most compression algorithms work best on textual data.

Sure, that's why I'm suggesting something fast like LZO (we could of course ignore images too). I'm not saying this is a high priority or anything . The idea isn't limited to just AU, either. Possible applications are everywhere.

EDIT:
Client/server communications, for example? (I don't know what the current system does)

Hi Fuzz,

ACSS will replace allegiance AU, and uses IIS GZIP compression for file transmits.

BackTrak wrote:QUOTE (BackTrak @ Feb 19 2012, 12:20 AM) Hi Fuzz,

ACSS will replace allegiance AU, and uses IIS GZIP compression for file transmits.

Good to know . So that just leaves the topic of using compression elsewhere.

BTW, Allegiance AU use HTTP.

So even current AU uses gzip HTTP compression (if server is configured correctly).

Well apparently http://asgs.alleg.net/asgsnet/main.aspx isn't using gzip compression, perhaps it should be turned on.

Same with the forum.