On October 03, 2003 03:40 pm, Ian Clarke wrote:
Toad wrote:
On Sun, Sep 28, 2003 at 12:21:05AM -0500, Brandon Low wrote:
Also, it is possible that inserts are __slow__ due (indirectly) to the
asyncronizing of trailer sends. I've tried to explain my view of this
to toad, but lets see if
On October 04, 2003 10:21 am, Toad wrote:
On Fri, Oct 03, 2003 at 11:40:25PM +0100, Toad wrote:
On Fri, Oct 03, 2003 at 12:40:03PM -0700, Ian Clarke wrote:
Toad wrote:
On Sun, Sep 28, 2003 at 12:21:05AM -0500, Brandon Low wrote:
Also, it is possible that inserts are __slow__ due
On October 04, 2003 11:19 am, Toad wrote:
On Sat, Oct 04, 2003 at 11:12:07AM -0400, Ed Tomlinson wrote:
On October 04, 2003 10:21 am, Toad wrote:
On Fri, Oct 03, 2003 at 11:40:25PM +0100, Toad wrote:
On Fri, Oct 03, 2003 at 12:40:03PM -0700, Ian Clarke wrote:
Toad wrote:
On
On Sat, 2003-10-04 at 13:55, Ed Tomlinson wrote:
In case you may be right. Once cvs works at some level again I will try.
Made the mistake of backing out all my changes and updating from cvs.
I does not even build, when I fix that (getIdleTime idleTime in OCM)
fproxy stalls... Unstable is,
On Sun, Sep 28, 2003 at 12:21:05AM -0500, Brandon Low wrote:
Threadlimits probably aren't the issue any more, can you check how many
queries per minute your node is accepting? There is a default in the
config file to only accept a max of 300 queries per minute, is it
possible that that is the
On Sun, Sep 28, 2003 at 12:46:09AM -0500, Salah Coronya wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Brandon Low wrote:
| Threadlimits probably aren't the issue any more, can you check how many
| queries per minute your node is accepting? There is a default in the
| config file to
Toad wrote:
On Sun, Sep 28, 2003 at 12:21:05AM -0500, Brandon Low wrote:
Also, it is possible that inserts are __slow__ due (indirectly) to the
asyncronizing of trailer sends. I've tried to explain my view of this
to toad, but lets see if mentioning it here gets me anywhere:
With trailers async,
On Fri, 2003-10-03 at 18:12, Salah Coronya wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Toad wrote:
|I've noticed some the previous builds (like 6205) were slow on splitfile
|inserts (and tended to hang on the last couple of blocks), but latest
|ones I can let a splitfile insert
On Fri, Oct 03, 2003 at 12:40:03PM -0700, Ian Clarke wrote:
Toad wrote:
On Sun, Sep 28, 2003 at 12:21:05AM -0500, Brandon Low wrote:
Also, it is possible that inserts are __slow__ due (indirectly) to the
asyncronizing of trailer sends. I've tried to explain my view of this
to toad, but lets
Hmm... *diffs 6205 and 6209*
I'll see if I can figure anything else out.
On Sun, 09/28/03 at 00:46:09 -0500, Salah Coronya wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Brandon Low wrote:
| Threadlimits probably aren't the issue any more, can you check how many
| queries per minute
On Sun, 2003-09-28 at 01:59, Brandon Low wrote:
Hmm... *diffs 6205 and 6209*
I'll see if I can figure anything else out.
Could it be the change I put it to be slightly more
accurate about the proportion of requests accepted
per hour by using requests out of the last 200
instead of out of the
I would severely doubt that... I'm a bit more suspicious of Niklas'
changes to localNIOInterface (probably of course just because they make
less sense to me.
I've made the diff from 6205-6209 from CVS (did it by date) if you don't
feel like messing with it (or for those w/o easy CVS access):
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
In build 6209 (and as far back as 6206/7), splitfile inserts are
painfully slow, to the point of where I though they weren't working at
all, but somehow I actually manager to get a block inserted (at HTL=25,
build 6209) . Even at HTL=1, splitfile
Threadlimits probably aren't the issue any more, can you check how many
queries per minute your node is accepting? There is a default in the
config file to only accept a max of 300 queries per minute, is it
possible that that is the limit you are hitting?
Also, it is possible that inserts are
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Brandon Low wrote:
| Threadlimits probably aren't the issue any more, can you check how many
| queries per minute your node is accepting? There is a default in the
| config file to only accept a max of 300 queries per minute, is it
| possible that
15 matches
Mail list logo
