On Friday 01 Aug 2003 17:17, Joe deBlaquiere wrote: > Couldn't we just consider local node's storage as a compressible > filesystem with the added benefit that when nodes happen to support (the > same) compression, they can just exchange the compressed data. If a node > requests the information and doesn't support compression, it has to be > decompressed before it is shipped. This way you don't break backward > compatibility (at least not immediately, a later policy to enforce > compression is an option).
No, that wouldn't work. All the files in the data store are encrypted. Encrypted data is be definition uncompressible. If it is not, then it is either by accident (highly unlikely), or there is a massive entropy inducing bug in the algorithm, i.e. the algrithm is broken. Therefore, compressing the data store would do nothing other than waste CPU cycles. Files must be compressed before they are encrypted to take advantage of compression. > My node is generally appears network IO bound, and it's a 450MHz P3 > laptop. I'm sure NGR topology improvements could help, but given the > need to maintain some amount of spare bandwidth (the marital harmony > issue thing) on a modest cable modem connection I don't think I can > really up the bandwidth... Compression would reduce your bandwidth consumption because all (well, ok, most/some) files being transferred would be compressed, thus smaller. So, to improve bandwidth shortages we have to either increase the available bandwidth (expensive and not always doable) or compress files that can be compressed (much cheaper, and always doable, data format allowing). Gordan _______________________________________________ devl mailing list [EMAIL PROTECTED] http://hawk.freenetproject.org:8080/cgi-bin/mailman/listinfo/devl
