Developer Only Discussion List

[Tony Smith <tony AT smee.org>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Friday 12 March 2004 10:31, Arwed von Merkatz wrote:
> On Fri, Mar 12, 2004 at 10:06:21AM +0000, Tony Smith wrote:
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA1
> >
> > All,
> >
> > Yesterday someone (who shall remain nameless) performed a large sync of
> > *everything* in our repository and it essentially used 100% of the ADSL
> > link in our office while it was going on (the 2Mb downstream link was
> > fine, but we only have 256k upstream). I killed it but it was restarted
> > shortly afterwards. Needless to say my colleagues were unimpressed.
> >
> > To prevent it from happening again, I'm going to put in place some
> > resource limits to limit the amount of data people can transfer in a
> > single command. If I get these limits wrong and commands that you think
> > are reasonable start getting rejected, please let me know.
> >
> > I'll also be writing a spell for the perforce-proxy server which caches
> > revisions locally to the client and I'll ask people to use that to help
> > keep the bandwidth usage down a little.
> >
> > Thanks for your help with this.
>
> I guess that's what is causing this:
> arwed@Otherland:~/Work/sm-perforce$ p4 sync
> Too many rows scanned (over 120000); see 'p4 help maxscanrows'.
>
> I have devel, test, stable, z-rejected, games and sorcery in my
> workspacec (as i need them all).
> Several others (worf, unet) also reported this problem.

No, that's the solution rather than the problem. For those of you that want 
everything, you'll need to sync them one branch at a time:

        p4 sync devel/...
        p4 sync test/...
        p4 sync games/...
        ...

This is my solution for now, but in the longer term I'm either going to (a) 
take this box home so you guys saturate my personal ADSL line or (b) learn 
about IP traffic shaping and patch my kernel to support it. 

Tony
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFAUZKbqu4dCYpCBl0RAhSqAJ4y+RtmD06KMTtsxmDYLpTk6eJzQACfWDBQ
76kJTp4YpDFUUJF09azRpOk=
=UyFj
-----END PGP SIGNATURE-----