[prev in list] [next in list] [prev in thread] [next in thread]
List: nepomuk
Subject: Re: [Nepomuk] On-battery indexing
From: Vishesh Handa <me () vhanda ! in>
Date: 2012-05-12 22:11:43
Message-ID: CAOPTMKBxP9OJu2SK1t0prGubu4_g1j_+8LH9VzpKMrCoNeAbWg () mail ! gmail ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
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 <Martin@lichtvoll.de>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
[Attachment #5 (text/html)]
Hey Raveendra<br><br>Would you be interested in tackling the problem? It's not \
that hard, and would help you familiarize yourself with the Nepomuk code \
base.<br><br>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.<br> <br>Let me know<br><br>PS: Make sure you reply to all<br><br><div \
class="gmail_quote">On Sat, May 12, 2012 at 4:05 PM, Martin Steigerwald <span \
dir="ltr"><<a href="mailto:Martin@lichtvoll.de" \
target="_blank">Martin@lichtvoll.de</a>></span> wrote:<br> <blockquote \
class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex">Am Sonntag, 6. Mai 2012 schrieb Vishesh Handa:<br> <div \
class="im">> > Could we do a limited indexing (a few files here and there, \
not<br> > > entire filesystems) when the user is on battery without much \
impact<br> > > on battery?<br>
><br>
> Yup. It is possible.<br>
><br>
> And in fact it wouldn't be too hard to implement.<br>
><br>
> Right now we have a kind of priority queue where files and folders and<br>
> queued. Routine scanning and indexing of files are given a lower<br>
> priority than files that are added by inotify. So, we just need to<br>
> make sure that only files with this higher priority are indexed when<br>
> the indexer is suspended.<br>
<br>
</div>Would be good for newly added files. And probably should be slower, lighter<br>
on resources than usual indexing.<br>
<br>
Not for the initial scan of everything.<br>
<span class="HOEnZb"><font color="#888888"><br>
--<br>
Martin 'Helios' Steigerwald - <a href="http://www.Lichtvoll.de" \
target="_blank">http://www.Lichtvoll.de</a><br>
GPG: 03B0 0D6C 0040 0710 4AFA B82F 991B EAAC A599 84C7<br>
</font></span></blockquote></div><br><br clear="all"><br>-- <br><span \
style="color:rgb(192,192,192)">Vishesh Handa</span><br><br>
_______________________________________________
Nepomuk mailing list
Nepomuk@kde.org
https://mail.kde.org/mailman/listinfo/nepomuk
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic