Lower default socket timeout for buildout?
Hi, in the last week I noticed that reducing buildout's socket timeout to something relatively low (3-5 seconds) made a lot of buildouts go much faster. It looks like various package metadata points off to bad servers that hang. I haven't had a buildout fail on me because of setting such a low timeout -- I only got annoyed when running with the longer default. I wonder whether it might be an idea to lower the default in general? Christian -- Christian Theune · ct@gocept.com gocept gmbh & co. kg · forsterstraße 29 · 06112 halle (saale) · germany http://gocept.com · tel +49 345 1229889 7 · fax +49 345 1229889 1 Zope and Plone consulting and development
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 01.02.2009 20:54 Uhr, Christian Theune wrote:
Hi,
in the last week I noticed that reducing buildout's socket timeout to something relatively low (3-5 seconds) made a lot of buildouts go much faster.
It looks like various package metadata points off to bad servers that hang.
I haven't had a buildout fail on me because of setting such a low timeout -- I only got annoyed when running with the longer default.
I wonder whether it might be an idea to lower the default in general?
At least I added a patch to buildout at some time ago in order to make the default timeout configurable through a command-line option (or was it a buildout options - I can't remember). ANdreas -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkmGilQACgkQCJIWIbr9KYxniACfeknh7k4e/dHUnuZgU1KaLf+R cTAAnRlXq+ZdqUpgdabevTgNlJ+A/XVQ =eMvM -----END PGP SIGNATURE-----
On Mon, 02 Feb 2009 06:53:24 +0100 Andreas Jung <lists@zopyx.com> wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 01.02.2009 20:54 Uhr, Christian Theune wrote:
Hi,
in the last week I noticed that reducing buildout's socket timeout to something relatively low (3-5 seconds) made a lot of buildouts go much faster.
It looks like various package metadata points off to bad servers that hang.
I haven't had a buildout fail on me because of setting such a low timeout -- I only got annoyed when running with the longer default.
I wonder whether it might be an idea to lower the default in general?
At least I added a patch to buildout at some time ago in order to make the default timeout configurable through a command-line option (or was it a buildout options - I can't remember).
It's only a command line option right now. Making it configurable through a buildout option would be nice too. -- Christian Theune · ct@gocept.com gocept gmbh & co. kg · forsterstraße 29 · 06112 halle (saale) · germany http://gocept.com · tel +49 345 1229889 7 · fax +49 345 1229889 1 Zope and Plone consulting and development
Christian Theune wrote:
It's only a command line option right now.
Which one?
Making it configurable through a buildout option would be nice too.
Yes, so it can live in default.cfg! Chris -- Simplistix - Content Management, Zope & Python Consulting - http://www.simplistix.co.uk
On Fri, 06 Feb 2009 12:42:37 +0000 Chris Withers <chris@simplistix.co.uk> wrote:
Christian Theune wrote:
It's only a command line option right now.
Which one?
-t
Making it configurable through a buildout option would be nice too.
Yes, so it can live in default.cfg!
Exactly. -- Christian Theune · ct@gocept.com gocept gmbh & co. kg · forsterstraße 29 · 06112 halle (saale) · germany http://gocept.com · tel +49 345 1229889 0 · fax +49 345 1229889 1 Zope and Plone consulting and development
Am 06.02.2009 um 14:21 schrieb Christian Theune:
On Fri, 06 Feb 2009 12:42:37 +0000 Chris Withers <chris@simplistix.co.uk> wrote:
Christian Theune wrote:
It's only a command line option right now.
Which one?
-t
Making it configurable through a buildout option would be nice too.
Yes, so it can live in default.cfg!
Exactly.
How did you add the -t option to default.cfg? It seems that I'm missing something to get it working. Yours sincerely, -- Michael Howitz · mh@gocept.com · software developer gocept gmbh & co. kg · forsterstraße 29 · 06112 halle (saale) · germany http://gocept.com · tel +49 345 1229889 8 · fax +49 345 1229889 1 Zope and Plone consulting and development
On Wed, 11 Feb 2009 09:18:19 +0100 Michael Howitz <mh@gocept.com> wrote:
Am 06.02.2009 um 14:21 schrieb Christian Theune:
On Fri, 06 Feb 2009 12:42:37 +0000 Chris Withers <chris@simplistix.co.uk> wrote:
Christian Theune wrote:
It's only a command line option right now.
Which one?
-t
Making it configurable through a buildout option would be nice too.
Yes, so it can live in default.cfg!
Exactly.
How did you add the -t option to default.cfg? It seems that I'm missing something to get it working.
The point of this discussion is that you can't but that it would be a good idea to be able to. ;) -- Christian Theune · ct@gocept.com gocept gmbh & co. kg · forsterstraße 29 · 06112 halle (saale) · germany http://gocept.com · tel +49 345 1229889 0 · fax +49 345 1229889 1 Zope and Plone consulting and development
Andreas Jung wrote:
At least I added a patch to buildout at some time ago in order to make the default timeout configurable through a command-line option (or was it a buildout options - I can't remember).
Would be good to know where this lives and/or how Christian was limiting the timeout for him... cheers, Chris -- Simplistix - Content Management, Zope & Python Consulting - http://www.simplistix.co.uk
participants (4)
-
Andreas Jung -
Chris Withers -
Christian Theune -
Michael Howitz