Re: My experience with kmail (was:Goodbye for now, kmail)

Sérgio Basto <[email protected]>
Newsgroups gmane.comp.kde.users.pim
Message-ID <[email protected]>
On Sat, 2017-08-26 at 00:27 +0100, Sérgio Basto wrote:
> On Sun, 2017-06-11 at 21:22 +0100, Sérgio Basto wrote:
> > On Sun, 2017-05-14 at 13:50 +0100, Sérgio Basto wrote:
> > > Hello 
> > > I just want thank you for who alert me for akonodi consume cpu
> > > problems
> > > , since a year ago I started have problems, the most notable was
> > > with
> > > firefox very slow consuming high level of CPU more than 100%, all
> > > system slow , after a while I discover that clean kde cache
> > > [1]  ,
> > > and reboot fix the problem for a while , problems usually just
> > > appears when I go to a place where internet is not stable ( some
> > > offices that internet goes down etc) but after do (5 days ago):
> > > 
> > > 	akonadictl stop
> > > 
> > > all problems are gone, my laptop now is bullet prove , Firefox
> > > doesn't
> > > consume more than 15% of CPU , even when in stress, when before
> > > consume
> > > more than 100% of one core , I got 4 . 
> > 
> > After check, not only akonadi consume 100% CPU I some
> > circumstances,
> > also firefox have the same symptoms, it happens when iwlwifi (intel
> > wireless) goes down ...  
> 
> JFTR
> 
> After digging and search all possible causes , I understood that was
> my
> kinit4 process and after one week I can say that was xrender option,
> system settings -> configure desktop effects -> advance -> composite
> type , was a non default xrender and when change it to opengl 2.0 ,
> (my
> intel graphics don't have opengl 3.0) I stop have very slow computer
> and 
> warnings like this : kernel: perf: interrupt took too long (42002 >
> 41952), lowering kernel.perf_event_max_sample_rate to 4000
> 
> Also akonadi works much better . 

Sorry but think I should report it again , this end ups that maybe all
is related with xorg-x11-drv-intel-2.99.917-26.20160929.fc25.x86_64 and
newer kernels. 
Using what is the default drive of F26 ("modesetting") seems fixes the
problem and seems that is the root of the problem (xorg-x11-drv-intel-
2.99.917-26.20160929.fc25.x86_64) [2] not kde itself.

[2]
https://bugzilla.redhat.com/show_bug.cgi?id=1413251

> > > [1] cd /home/sergio/.kde; ls -l 
> > > rm -rf /var/tmp/kdecache-sergio /run/user/500/ksocket-sergio
> > > /tmp/kde-sergio 
> > > 
> > > Conclusion, looks to me that akonodi starts something like "a
> > > thread
> > > looping" which is not visible in top command nor another system
> > > monitor
> > > tools , but can affect all system ... , have some way to debug
> > > the
> > > problem could be useful. 
> > > 
> > > Best regards,
-- 
Sérgio M. B.
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.