[Monotone-devel] Re: url schemes

[Koen Kooi]

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

Markus Schiltknecht schreef:
| Hi,
|
| Koen Kooi wrote:
|> Since it's read-only, is it possible to cache the state and allow
|> multiple connections?
|
| Hm.. if it uses mtn automate behind the scenes, as I did in my
| experiments, I fear that makes not much difference. (Except nuskool
| being faster than netsync anyway.)
|
|> At OpenEmbedded we have at any given moment >10
|> simultanous connections to mtn serve, which each take a few seconds to
|> 'initialize'[1] (incrementing rev and cert counters) and seem to block
|> other transfers ("Why do I have to wait 3 hours before I an allowed to
|> push a rev?!?" as one developer put it).
|
| Maybe http caching could help here? By reducing locking contention to
| the database, only requests which really need to write the database need
| to block each other.
|
| This is another good reason to keep the URL scheme simple. If you stuff
| too much information into a single request, caching it gets harder or
| useless.

Last week we had a maximum 173 simultanious[1] connections which put mtn
in such a state it needed to be killed to get traffic flowing again. So
having some form of relatively lock-free read-only serving option would
be a good thing.

regards,

Koen

[1] probably a lot of 'duplicate' connections where people ctrl-c and
try again and the server hasn't noticed the disconnect yet.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)

iD8DBQFH7pLJMkyGM64RGpERAulRAJ0Qx3x0AaXFUl2ScGNaGi6fQfVP3ACfcwO9
xnhltT5QflGoxrGAC7oZUrI=
=wOcv
-----END PGP SIGNATURE-----