also sprach martin f krafft [2010.03.16.1900 +0100]:
> I use ext4 with data=ordered, and while notmuch is writing the
> Xapian database, most I/O stalls on the machine:
>
> - Firefox does not get any mouse events
> - Vim blocks writing the viminfo file
> - All disk operations queue for mult
also sprach martin f krafft [2010.03.16.1900 +0100]:
> I use ext4 with data=ordered, and while notmuch is writing the
> Xapian database, most I/O stalls on the machine:
>
> - Firefox does not get any mouse events
> - Vim blocks writing the viminfo file
> - All disk operations queue for mult
On Tue, 16 Mar 2010 08:37:54 -0700 (PDT), Ben Gamari wrote:
> On Tue, 16 Mar 2010 11:08:47 +, Olly Betts wrote:
> > For the issue of a background task interfering with interactive use, the
> > feel
> > arguably matters more than the throughput.
> >
> > I'll probably put that patch in 1.0.19
also sprach Aneesh Kumar K. V
[2010.03.16.1810 +0100]:
> Ext3 fsync related issue is a know problem due to the way journalling is
> handled in ext3. The solution for that would be data=writeback ( with
> its loss of data integrity ) or not yet upstreamed data=guarded. Another
> option would be to
On Tue, 16 Mar 2010 19:00:52 +0100, martin f krafft wrote:
> I use ext4 with data=ordered, and while notmuch is writing the
> Xapian database, most I/O stalls on the machine:
>
> - Firefox does not get any mouse events
> - Vim blocks writing the viminfo file
> - All disk operations queue fo
On Tue, 16 Mar 2010 19:00:52 +0100, martin f krafft
wrote:
> I use ext4 with data=ordered, and while notmuch is writing the
> Xapian database, most I/O stalls on the machine:
>
> - Firefox does not get any mouse events
> - Vim blocks writing the viminfo file
> - All disk operations queue f
On Mon, Mar 15, 2010 at 10:29:36AM -0700, Ben Gamari wrote:
> On Mon, 15 Mar 2010 09:29:35 + (UTC), Olly Betts
> wrote:
> > http://oligarchy.co.uk/xapian/patches/xapian-1.0.18-flint-group-fsyncs.patch
> >
> > What this does it to at least pair up the calls to fdatasync(). It's
> > possible
also sprach Aneesh Kumar K. V
[2010.03.16.1810 +0100]:
> Ext3 fsync related issue is a know problem due to the way journalling is
> handled in ext3. The solution for that would be data=writeback ( with
> its loss of data integrity ) or not yet upstreamed data=guarded. Another
> option would be to
On Tue, 16 Mar 2010 22:40:17 +0530, "Aneesh Kumar K. V"
wrote:
> Ext3 fsync related issue is a know problem due to the way journalling is
> handled in ext3. The solution for that would be data=writeback ( with
> its loss of data integrity ) or not yet upstreamed data=guarded. Another
> option wou
On Tue, 16 Mar 2010 22:40:17 +0530, "Aneesh Kumar K. V" wrote:
> Ext3 fsync related issue is a know problem due to the way journalling is
> handled in ext3. The solution for that would be data=writeback ( with
> its loss of data integrity ) or not yet upstreamed data=guarded. Another
> option woul
On Tue, 16 Mar 2010 08:37:54 -0700 (PDT), Ben Gamari
wrote:
> On Tue, 16 Mar 2010 11:08:47 +, Olly Betts wrote:
> > For the issue of a background task interfering with interactive use, the
> > feel
> > arguably matters more than the throughput.
> >
> > I'll probably put that patch in 1.0.1
On Tue, 16 Mar 2010 11:08:47 +, Olly Betts wrote:
> For the issue of a background task interfering with interactive use, the feel
> arguably matters more than the throughput.
>
> I'll probably put that patch in 1.0.19, and look at moving all the fdatasync()
> calls together. This is http://t
On Tue, 16 Mar 2010 11:08:47 +, Olly Betts wrote:
> For the issue of a background task interfering with interactive use, the feel
> arguably matters more than the throughput.
>
> I'll probably put that patch in 1.0.19, and look at moving all the fdatasync()
> calls together. This is http://t
On Mon, Mar 15, 2010 at 10:29:36AM -0700, Ben Gamari wrote:
> On Mon, 15 Mar 2010 09:29:35 + (UTC), Olly Betts wrote:
> > http://oligarchy.co.uk/xapian/patches/xapian-1.0.18-flint-group-fsyncs.patch
> >
> > What this does it to at least pair up the calls to fdatasync(). It's
> > possible to
On Mon, 15 Mar 2010 09:29:35 + (UTC), Olly Betts wrote:
> On 2010-03-15, Hans Dieter Pearcey wrote:
> > On Sun, 14 Mar 2010 22:59:28 -0700 (PDT), Ben Gamari wrote:
> >> Notmuch is using xapian 1.08-1.99karmic from the Xapian backports PPA,
> >> which
> >> I believe includes the recent databas
On Mon, 15 Mar 2010 09:29:35 + (UTC), Olly Betts wrote:
> On 2010-03-15, Hans Dieter Pearcey wrote:
> > On Sun, 14 Mar 2010 22:59:28 -0700 (PDT), Ben Gamari wrote:
> >> Notmuch is using xapian 1.08-1.99karmic from the Xapian backports PPA,
> >> which
> >> I believe includes the recent databas
On 2010-03-15, Hans Dieter Pearcey wrote:
> On Sun, 14 Mar 2010 22:59:28 -0700 (PDT), Ben Gamari wrote:
>> Notmuch is using xapian 1.08-1.99karmic from the Xapian backports PPA, which
>> I believe includes the recent database update optimizations.
>
> As far as I know, it doesn't. 1.0.18 is the st
On Sun, 14 Mar 2010 22:59:28 -0700 (PDT), Ben Gamari wrote:
> Notmuch is using xapian 1.08-1.99karmic from the Xapian backports PPA, which
> I believe includes the recent database update optimizations.
As far as I know, it doesn't. 1.0.18 is the stable version in which it was
fixed.
http://trac
On 2010-03-15, Hans Dieter Pearcey wrote:
> On Sun, 14 Mar 2010 22:59:28 -0700 (PDT), Ben Gamari wrote:
>> Notmuch is using xapian 1.08-1.99karmic from the Xapian backports PPA, which
>> I believe includes the recent database update optimizations.
>
> As far as I know, it doesn't. 1.0.18 is the st
On Sun, 14 Mar 2010 22:59:28 -0700 (PDT), Ben Gamari
wrote:
> Notmuch is using xapian 1.08-1.99karmic from the Xapian backports PPA, which
> I believe includes the recent database update optimizations.
As far as I know, it doesn't. 1.0.18 is the stable version in which it was
fixed.
http://tra
Out of curiosity: How does notmuch perform for you?
I just started using it on a daily basis last week. I love the power that
notmuch provides and the emacs interface is surprisingly usable after you've
gotten used to it, but that being said, I've been quite surprised by how poorly
the kernel resp
Out of curiosity: How does notmuch perform for you?
I just started using it on a daily basis last week. I love the power that
notmuch provides and the emacs interface is surprisingly usable after you've
gotten used to it, but that being said, I've been quite surprised by how poorly
the kernel resp
22 matches
Mail list logo
