On Saturday 14 May 2011 02:53:25 Dennis Nezic wrote:
> On Wed, 11 May 2011 17:48:36 +0100, Matthew Toseland wrote:
> > On Wednesday 11 May 2011 02:31:51 Dennis Nezic wrote:
> > > On Fri, 6 May 2011 15:55:59 -0400, Dennis Nezic wrote:
> > > > On Fri, 6 May 2011 18:57:13 +0100, Matthew Toseland wrote
On Wed, 11 May 2011 17:48:36 +0100, Matthew Toseland wrote:
> On Wednesday 11 May 2011 02:31:51 Dennis Nezic wrote:
> > On Fri, 6 May 2011 15:55:59 -0400, Dennis Nezic wrote:
> > > On Fri, 6 May 2011 18:57:13 +0100, Matthew Toseland wrote:
> > > > On Thursday 05 May 2011 03:26:45 Dennis Nezic wrote
On Wednesday 11 May 2011 02:31:51 Dennis Nezic wrote:
> On Fri, 6 May 2011 15:55:59 -0400, Dennis Nezic wrote:
> > On Fri, 6 May 2011 18:57:13 +0100, Matthew Toseland wrote:
> > > On Thursday 05 May 2011 03:26:45 Dennis Nezic wrote:
> > > > For the past several builds, I'm not sure exactly when the
On Fri, 6 May 2011 15:55:59 -0400, Dennis Nezic wrote:
> On Fri, 6 May 2011 18:57:13 +0100, Matthew Toseland wrote:
> > On Thursday 05 May 2011 03:26:45 Dennis Nezic wrote:
> > > For the past several builds, I'm not sure exactly when the issue
> > > started, before build01364 at least, my node expe
On Fri, 6 May 2011 18:57:13 +0100, Matthew Toseland wrote:
> On Thursday 05 May 2011 03:26:45 Dennis Nezic wrote:
> > For the past several builds, I'm not sure exactly when the issue
> > started, before build01364 at least, my node experiences quite high
> > disk IO, which bogs down my computer. I
On Thursday 05 May 2011 03:26:45 Dennis Nezic wrote:
> For the past several builds, I'm not sure exactly when the issue
> started, before build01364 at least, my node experiences quite high
> disk IO, which bogs down my computer. I think once I left it alone, and
> it resolved itself after a few ho
