[Kde-pim] Review Request 111469: Don't use 1.5 GB of memory when importing big maildir

[Milian Wolff]

-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/111469/#review35884
-----------------------------------------------------------



resources/maildir/retrieveitemsjob.cpp
<http://git.reviewboard.kde.org/r/111469/#comment26570>

    While this is already committed, why not create a new job as soon as the job count is below MaxSubJobs? This way one would create 300 jobs, wait for all of them finish, create the next 300 and so on, or am I misunderstanding the code?


- Milian Wolff


On July 11, 2013, 9:51 a.m., Sergio Luis Martins wrote:
> 
> -----------------------------------------------------------
> This is an automatically generated e-mail. To reply, visit:
> http://git.reviewboard.kde.org/r/111469/
> -----------------------------------------------------------
> 
> (Updated July 11, 2013, 9:51 a.m.)
> 
> 
> Review request for KDEPIM and Volker Krause.
> 
> 
> Description
> -------
> 
> The code was creating 70k ItemCreateJobs first, and then starting them all. That makes mem usage reach a peak of 1.5GB here.
> It does have code to do one event loop iteration every 20 e-mails, but that only makes it fire one ItemCreateJob, so they pile up anyway.
> 
> Solution is to throttle ItemCreationJob creation.
> 
> CPU-wise, this solution and the old one are equivalent, they are both equally fast.
> 
> 
> Diffs
> -----
> 
>   resources/maildir/retrieveitemsjob.cpp 6afedec 
>   resources/maildir/retrieveitemsjob.h dfc7095 
> 
> Diff: http://git.reviewboard.kde.org/r/111469/diff/
> 
> 
> Testing
> -------
> 
> Imported a big maildir. Mem goes to 60MB max
> 
> 
> Thanks,
> 
> Sergio Luis Martins
> 
>

_______________________________________________
KDE PIM mailing list kde-pim at kde.org
https://mail.kde.org/mailman/listinfo/kde-pim
KDE PIM home page at http://pim.kde.org/