Re: [Monotone-devel] Fatal error: std::runtime_error

[Jens Seidel]

On Wed, Apr 11, 2007 at 04:16:07PM +0200, Markus Schiltknecht wrote:
> Jens Seidel wrote:
> >Because of the last column in the output:
> >mtn: Bytes rein | Bytes raus | Zertifikate rein | Revisionen rein
> >mtn:    192,0 k |    105,2 k |           52/132 |           33/33
> 
> Ah, sure. But in this case here, you are still missing 80 certificates, no?

My fault. I copied the output before it finished and edited it later.

> >This remembers me that I had to restart monotone during the last large
> >update every 100-200 revisions because it froze. It was really funny:
> >I started it, waited approx. 30 minutes until it hung, stopped it using
> >Ctrl+C, restarted, waited, killed, ... (many times).
> 
> I assume you would have got a TCP timeout sooner or later, if you didn't
> terminate monotone before that. Or the TCP connection would have been

Yes, than I probably get the same std::runtime exception I reported initially:
mtn: Fatal error: std::runtime_error: network error: recv failure: time of
waiting for the connection expired (my translation)

I have seen this message only once for now. Probably I terminated it
before.

> able to resume. What connection are you on?

A DSL flatrate, 6016 kBit/s.

> >But currently it is just to slow.
> 
> Uhm.. yeah.. netsync only or is there something else you think is too slow?

It's the CPU usage IIRC. Monotone uses 97% CPU time during fetch of
revisions on my 800 MHz PIII subnotebook. I still have a 300 MHz Mips
box and a SGI Octane (2x270 MHz R12000 Mips CPUs) but it's probably not
a good idea to start mtn on these boxes.

> You might want to upgrade to the newest monotone release. Binary

Will do so.

> Okay, I've tried to pull the openembedded repository from scratch. After 
> six hours, these are my results:
> 
> $ mtn --version
> monotone 0.33 (base revision: cfebc8eb7049def476cc5fd61fef64eb14120e68)
> 
> $ time mtn -d oe.db pull monotone.openembedded.org "*"
> mtn:  bytes in | bytes out |      certs in |       revs in
> mtn:    63.4 M |       462 | 42,548/64,630 | 10,686/16,148
> mtn: error: I/O failure while talking to peer monotone.openembedded.org, 
> disconnecting

Not so bad, you could fetch 10,686 during a single attempt!

> mtn:  bytes in | bytes out |      certs in |     revs in
> mtn:    37.3 M |     2.0 M | 22,082/22,082 | 5,462/5,462
> mtn: error: I/O failure while talking to peer monotone.openembedded.org, 
> disconnecting

Ah, failure after the last revision was fetch. The same happens for me
too.

Jens