---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/116692/
---
(Updated July 10, 2014, 4:14 p.m.)
Status
--
This change has been di
> On March 21, 2014, 10:58 a.m., Christian Mollekopf wrote:
> > It turned out that most of the memory was used the ItemFetchJob loading all
> > items into memory. We've now optimized this, and for me the indexer never
> > goes beyond ~250MB (initial indexing), and during normal usage stays arou
---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/116692/#review53637
---
It turned out that most of the memory was used the ItemFetchJo
---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/116692/#review53035
---
I've been doing some simple tests which are similar to your pa
On Monday 10 March 2014 10:08:29 Aaron J. Seigo wrote:
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://git.reviewboard.kde.org/r/116692/
> ---
>
> Review re
[ Comments below, in-line ]
On 03/10/2014 09:43 AM, Aaron J. Seigo wrote:
As an aside, when reading emails, deleting them, etc. they are
individually indexed with a commit coming afterwards. That means
significant writes to disk which, on my 3 year old laptop with a
rotating disk for storage, ta
> On March 10, 2014, 11:54 a.m., Sergio Luis Martins wrote:
> > Memory usage seems stable now, but it's taking forever to index. 10 minutes
> > has passed and it's still indexing a 70k mail folder.
> > CPU is at 1%. IO is at 100%.
> >
> > On a SSD... This is worse than the memory problem IMHO.
> On March 10, 2014, 11:54 a.m., Sergio Luis Martins wrote:
> > Memory usage seems stable now, but it's taking forever to index. 10 minutes
> > has passed and it's still indexing a 70k mail folder.
> > CPU is at 1%. IO is at 100%.
> >
> > On a SSD... This is worse than the memory problem IMHO.
> On March 10, 2014, 11:54 a.m., Sergio Luis Martins wrote:
> > Memory usage seems stable now, but it's taking forever to index. 10 minutes
> > has passed and it's still indexing a 70k mail folder.
> > CPU is at 1%. IO is at 100%.
> >
> > On a SSD... This is worse than the memory problem IMHO.
> On March 10, 2014, 11:54 a.m., Sergio Luis Martins wrote:
> > Memory usage seems stable now, but it's taking forever to index. 10 minutes
> > has passed and it's still indexing a 70k mail folder.
> > CPU is at 1%. IO is at 100%.
> >
> > On a SSD... This is worse than the memory problem IMHO.
> On March 10, 2014, 11:54 a.m., Sergio Luis Martins wrote:
> > Memory usage seems stable now, but it's taking forever to index. 10 minutes
> > has passed and it's still indexing a 70k mail folder.
> > CPU is at 1%. IO is at 100%.
> >
> > On a SSD... This is worse than the memory problem IMHO.
---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/116692/#review52518
---
Memory usage seems stable now, but it's taking forever to inde
[ Comments below, in-line ]
On 03/10/2014 07:21 AM, Aaron J. Seigo wrote:
It's not the precise patch, no. The main functional difference is
that it lowers the commit limit from 500 to 100.
Hi,
Would it be possible for the patch (or a subsequent refactor) to
recognize an environment variable
> On March 10, 2014, 10:18 a.m., Sergio Luis Martins wrote:
> > Hi, Is this the same patch I tested a few days ago ? That one didn't fix
> > the problem, I still reach 1.5GB of memory usage with a 100k e-mail maildir.
>
> Dan Vrátil wrote:
> There is still the problem with Akonadi/KMime "le
---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/116692/
---
(Updated March 10, 2014, 11:12 a.m.)
Review request for Akonadi and Baloo
> On March 10, 2014, 11:18 a.m., Sergio Luis Martins wrote:
> > Hi, Is this the same patch I tested a few days ago ? That one didn't fix
> > the problem, I still reach 1.5GB of memory usage with a 100k e-mail maildir.
There is still the problem with Akonadi/KMime "leaking" lots and lots of
mem
---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/116692/#review52509
---
Hi, Is this the same patch I tested a few days ago ? That one
---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/116692/
---
Review request for Akonadi and Baloo.
Repository: baloo
Description
---
18 matches
Mail list logo
