in reply to Re (tilly) 1: Serving tarball contents as part of your webspace (impractical but fun)
in thread Serving tarball contents as part of your webspace (impractical but fun)

Thatís why I tried Archive::Zip - zipfiles contain individually compressed files. However, as I said, performance improved only marginally at best. The problem that you get a multitude of simultaneously running scripts all doing the same, very CPU intensive thing remains, after all. Losing the tarball is not helpful since the main idea was to keep a document tree that consists of oodles of tiny snippet files from eating an ungodly amount of inodes.

Youíre giving me an idea though Ė Iíll check to see how it performs with an uncompressed zipfile. I know uncompressed tarballs wonít make a huge difference since Archive::Tar always slurps the whole tarball into memory no matter what. However, zipfiles are indexed, and maybe Archive::Zip is smart enough to exploit that in which case this thing may actually be useful.

Iíll update as soon as Iíve found the time to run a quick check.

  • Comment on Re^2: Serving tarball contents as part of your webspace (impractical but fun)