From nepomuk Sat May 12 22:11:43 2012 From: Vishesh Handa Date: Sat, 12 May 2012 22:11:43 +0000 To: nepomuk Subject: Re: [Nepomuk] On-battery indexing Message-Id: X-MARC-Message: https://marc.info/?l=nepomuk&m=133686014418085 MIME-Version: 1 Content-Type: multipart/mixed; boundary="--===============7347385575462420097==" --===============7347385575462420097== Content-Type: multipart/alternative; boundary=f46d04088e3d6d226904bfddf82d --f46d04088e3d6d226904bfddf82d Content-Type: text/plain; charset=ISO-8859-1 Hey Raveendra Would you be interested in tackling the problem? It's not that hard, and would help you familiarize yourself with the Nepomuk code base. The relevant code is in kde-runtime/nepomuk/services/fileindexer/. The code is also there in nepomuk-core/services/fileindexer. You can choose either of them, though we would prefer nepomuk-core, as kde-runtime/nepomuk will soon be deleted. Let me know PS: Make sure you reply to all On Sat, May 12, 2012 at 4:05 PM, Martin Steigerwald wrote: > Am Sonntag, 6. Mai 2012 schrieb Vishesh Handa: > > > Could we do a limited indexing (a few files here and there, not > > > entire filesystems) when the user is on battery without much impact > > > on battery? > > > > Yup. It is possible. > > > > And in fact it wouldn't be too hard to implement. > > > > Right now we have a kind of priority queue where files and folders and > > queued. Routine scanning and indexing of files are given a lower > > priority than files that are added by inotify. So, we just need to > > make sure that only files with this higher priority are indexed when > > the indexer is suspended. > > Would be good for newly added files. And probably should be slower, lighter > on resources than usual indexing. > > Not for the initial scan of everything. > > -- > Martin 'Helios' Steigerwald - http://www.Lichtvoll.de > GPG: 03B0 0D6C 0040 0710 4AFA B82F 991B EAAC A599 84C7 > -- Vishesh Handa --f46d04088e3d6d226904bfddf82d Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hey Raveendra

Would you be interested in tackling the problem? It= 9;s not that hard, and would help you familiarize yourself with the Nepomuk= code base.

The relevant code is in kde-runtime/nepomuk/services/fil= eindexer/. The code is also there in nepomuk-core/services/fileindexer. You= can choose either of them, though we would prefer nepomuk-core, as kde-run= time/nepomuk will soon be deleted.

Let me know

PS: Make sure you reply to all

On Sat, May 12, 2012 at 4:05 PM, Martin Steigerwald <Marti= n@lichtvoll.de> wrote:
Am Sonntag, 6. Mai 2012 schrieb Vishesh Hand= a:
> > Could we do a limited indexing (a few files her= e and there, not
> > entire filesystems) when the user is on battery without much impa= ct
> > on battery?
>
> Yup. It is possible.
>
> And in fact it wouldn't be too hard to implement.
>
> Right now we have a kind of priority queue where files and folders and=
> queued. Routine scanning and indexing of files are given a lower
> priority than files that are added by inotify. So, we just need to
> make sure that only files with this higher priority are indexed when > the indexer is suspended.

Would be good for newly added files. And probably should be slower, l= ighter
on resources than usual indexing.

Not for the initial scan of everything.

--
Martin 'Helios' Steigerwald - http://www.Lichtvoll.de
GPG: 03B0 0D6C 0040 0710 4AFA =A0B82F 991B EAAC A599 84C7



--
Vishesh Handa

--f46d04088e3d6d226904bfddf82d-- --===============7347385575462420097== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Nepomuk mailing list Nepomuk@kde.org https://mail.kde.org/mailman/listinfo/nepomuk --===============7347385575462420097==--