bvk@hhb.UUCP (Brett Kuehner) (01/27/89)
In article <2169@van-bc.UUCP> lphillips@lpami.wimsey.bc.ca (Larry Phillips) writes: > > Um... I'm running the release version of 1.3 and I have my stack set to > 30000, and I occasionly get zoo seemingly just looping while trying to read > a zoo archive. It doesn't crash (I can break it), but it is annoying to > have to the zoo archive to ram: to look at it. I don't recall offhand what > else I have running in the background that may effect things. > > fred Is this when your zoo archive is in a directory with a lot of files in it? I have a directory on my HD with about 50 files in it. If I do a "zoo l foo.zoo", where foo.zoo is in that directory, zoo appears to thrash on the drive a lot, possibly reading in the name of each file in the HD directory (and very slowly). It will eventually list the archive, though. This happened with zoo 1.42, and I believe it happens with zoo 2.00 as well (I'll have to make sure that's what I ran). The amount of disk thrashing that goes on is definitely related to the number of files in the HD directory. Could someone with the source check out why this might happen? (or is this known and fixed in 2.01?) Brett -- Brett Kuehner ...!princeton!hhb!bvk bvk%hhb@princeton.EDU
grwalter@watmath.waterloo.edu (Fred Walter) (01/28/89)
In article <171@hhb.UUCP> bvk@hhb.UUCP (Brett Kuehner) writes: >Is this when your zoo archive is in a directory with a lot of files in it? I >have a directory on my HD with about 50 files in it. If I do a >"zoo l foo.zoo", where foo.zoo is in that directory, zoo appears to thrash >on the drive a lot, possibly reading in the name of each file in the >HD directory (and very slowly). It will eventually list the archive, though. Yes this is what happens with me. I never before waited to see how long it would take for a listing to appear (1 MINUTE 26 SECONDS in a directory with 93 files in it).
ejkst@cisunx.UUCP (Eric J. Kennedy) (01/29/89)
In article <23314@watmath.waterloo.edu> grwalter@watmath.waterloo.edu (Fred Walter) writes: >In article <171@hhb.UUCP> bvk@hhb.UUCP (Brett Kuehner) writes: >>Is this when your zoo archive is in a directory with a lot of files in it? I >>have a directory on my HD with about 50 files in it. If I do a >>"zoo l foo.zoo", where foo.zoo is in that directory, zoo appears to thrash >>on the drive a lot, possibly reading in the name of each file in the >>HD directory (and very slowly). It will eventually list the archive, though. > >Yes this is what happens with me. I never before waited to see how long it >would take for a listing to appear (1 MINUTE 26 SECONDS in a directory with >93 files in it). I've had it give me an error message something to the effect of "can't find foo*.zoo", when I just asked for "foo". If I type "zoo v foo" and I have foo.zoo and foobar.zoo in the directory, it will list both, after much thrashing and seeking. If I ask for "foo.zoo", it still thrashes and seeks, but only lists foo.zoo. This is using zoo 2.0. I much prefer zoo over arc, but this is my biggest gripe. I've had it spin for long minutes when trying to create an archive in a very large directory. (I switched to another cli and added 100 buffers to dh0:, which helped.) -- Eric Kennedy ejkst@cisunx.UUCP
blgardne@esunix.UUCP (Blaine Gardner) (01/30/89)
From article <23314@watmath.waterloo.edu>, by grwalter@watmath.waterloo.edu (Fred Walter): > In article <171@hhb.UUCP> bvk@hhb.UUCP (Brett Kuehner) writes: >>Is this when your zoo archive is in a directory with a lot of files in it? I >>have a directory on my HD with about 50 files in it. If I do a >>"zoo l foo.zoo", where foo.zoo is in that directory, zoo appears to thrash >>on the drive a lot, possibly reading in the name of each file in the >>HD directory (and very slowly). It will eventually list the archive, though. > > Yes this is what happens with me. I never before waited to see how long it > would take for a listing to appear (1 MINUTE 26 SECONDS in a directory with > 93 files in it). I just did a little testing and Zoo does filename expansion whether you ask it to or not. Zoo v ami is treated just the same as Zoo v ami* So if you have your zoo file in a directory with a lot of entries (120 in my case) it will take a while to find the right file. It takes between 7 and 10 seconds on my hard drive (with 200 buffers), I can imagine how slow this would be on floppies. -- Blaine Gardner @ Evans & Sutherland 580 Arapeen Drive, SLC, Utah 84108 Here: utah-cs!esunix!blgardne {ucbvax,allegra,decvax}!decwrl!esunix!blgardne There: uunet!iconsys!caeco!pedro!worsel!blaine "Nobody will ever need more than 64K." "Nobody needs multitasking on a PC."