Bug 324586

When I enable the revamped Facebook resource in KDE 4.11.1, the Facebook resource fetches 4000 status updates from my timeline and the Akonadi-Nepomuk Feeder tries to index them all at once, triggering excessive CPU usage. When the Nepomuk Feeder is done, the Facebook resource fetches again more status updates, with more CPU used.

Both Akonadi Nepomuk Feeder and Facebook resource are working properly. This is more of a indexer strategy issue.

Suggestion: please, only index Facebook notifications (which the new Facebook resource can deliver separately) Don't index the bulk of timeline updates (almost always including Candy Crush, FarmVille, and other stupid updates).

Reproducible: Always

Steps to Reproduce:
1. Enable the new Facebook resource included on KDE 4.11.1
2. Let the Facebook resource download status updates.
Actual Results:  
The Akonadi Nepomuk Feeder will try to index my timeline, and will succeed, at the cost of lots of CPU cycles. However, since the timeline is refreshed on a timely basis, the net result is seeing a 100% CPU load most of the time.

Expected Results:  
The Akonadi Nepomuk Feeder only indexes notifications (at most, 20 items), with negligible spikes in CPU usage)

KDE 4.11.1, Fedora repositories. Facebook resource enabled and working well.