🚀 go-pugleaf

[ note followup-to: ]

In article <1992Sep18.091752.5004@newshost.anu.edu.au> G.Huston@aarnet.edu.au writes:
>Matthew Hannigan) writes:
>> Fingering it just now shows that a user from Ohio, one from Kyoto
>> and one from I think Germany were using archie.  If these people are
>> also ftping stuff it could be a bit costly.
>
>no - in terms of traffic incoming on the link all that gets transmitted is the 
>acks! 
>
>> Perhaps archie may be contributing to the problem!
>
>no  -  archie is doing an excellent job in providing a local cache of material
>which is far faster for the end client than pulling in  data  from  the  sites
>that  archie shadows. The real issue here is simply one of overwhelming volume
>of traffic on the incoming side - and the overall bulk of that incoming volume 
>is ftp pulls. As I noted in an earlier posting archie is helping here, but the 
>sheer total volume of traffic is now at a level where we are  facing  problems 
>of  quality  of  service  on this particular link. Archie simply cannot shadow 
>everything! 

Yeah, I was just joking about archie contributing to the problem ..
its just that it's so good its getting international customers.

Still, it could be made a _LOT_ better if we were able to restrict
the search to Oz sites - though you've proably heard that before.

Another concern I have had recently is that a lot of local material
doesn't seem up to date .. three things I had looked for recently
were months out of date with their overseas sites.  And these weren't
obscure bits of software.

Also, is it possible to ascertain what percentage of the ftp pulls
were, say, GIFS, and what were software?  Is it possible to look at packets,
(say, just make a sample) and grab the packet that has the filename
and then figure out what percentage of the FTPs were what?

Or do you think this is a bit intrusive?  Note that you don't have
to record who or where the stuff is coming to/from, just the name
of the document/program/picture.

I would be _very_ interested to know.

-Matt
matt@aodc20.aodc.gov.au