[SOLVED] Indexing wasting all the memory?

Aeris · 10-03-2013, 02:33 PM

I gave a glance to /system/Search Indexes/ folder on kindle paperwhite and BAM! Found that it take up 96.8 MB!

I've "only" 300 books so it is so pretty annoying that it take so much...

Is it safe to delete all these files? Must i keep ones with extensions .db an .lg? Would the database file become corrupted after this operation?

Obviously, I need also a way to block the indexer after doing this... I've searched in the forum but didn't find any solution that really works on paperwhite

Any idea?

Thank you in advance

hfpop · 10-03-2013, 03:55 PM

Hello,

I hate this as well. My solution was, however, different:

- forget about indexing;
- placed books in /mnt/us/books;
- modified kindle explorer to allow ONLY book copy to /mnt/us/documents (modified sources posted in the same thread).

In this way my books are NOT indexed. My books are invisible to Kindle. I only make visible books on an as needed basis.

I know, this is a solution deserving at most grade 8 on a 1-10 scale. But it is the best I could get so far. If anyone has any ideas on improving this, I am listening.

knc1 · 10-03-2013, 04:11 PM

sounds simple and effective.
that makes it hard to beat.

Aeris · 10-03-2013, 04:44 PM

Don't like it to much... I take ages to put nice covers on my books to have a nice looking library xD Damned indexer...

hfpop · 10-03-2013, 05:56 PM

By the way, I have the reversed problem: I want to create books using Calibre, but I want no covers. Without covers, the first image in the book becomes the cover. And I do not want this. My point: I want space for my books, i.e. text, not to look at nice covers. How can I create books with no covers? Thank you

Aeris · 10-03-2013, 06:08 PM

FOR ALREADY CONVERTED BOOKS:
In Calibre, selects all the book from which you want to remove the cover, right click on them, then Edit metadata -> Edit metadata in bulk -> Change cover -> Remove Cover -> Apply

FOR NEW BOOKS:
Preferences -> Output options -> No default cover -> Apply

ixtab · 10-03-2013, 06:19 PM

Easiest solution: use list view, instead of cover view, on the Kindle

. Not only is it less distracting, it's also more compact (it displays 8 books per page instead of 6).

Aeris · 10-03-2013, 06:23 PM

Cover view is sooo cute instead

P.S. I've just discovered that the number of pages at the bottom-right is clickable O.O

NiLuJe · 10-03-2013, 06:38 PM

@Aeris! It's also contextual

(for example, if you're sorting by author, you can jump to authors starting with a specific letter).

Aeris · 10-03-2013, 06:40 PM

Ohh great, didn't know!

Btw, we are a bit off-topic now... if somebody has an idea for stoppin' the fu*kin' indexer, I'm all ears!

ixtab · 10-03-2013, 06:57 PM

Quote:

Originally Posted by Aeris

Ohh great, didn't know!

Btw, we are a bit off-topic now... if somebody has an idea for stoppin' the fu*kin' indexer, I'm all ears!

There were a few attempts, but none of them (seem to) work reliably. As the pressure is building, this will probably also climb on the "take-a-look-at" priority list of the folks here, and might eventually get solved.

It's a shame that Amazon doesn't provide an out of the box option to disable it. It's causing tons of problems, and I don't think that more than 1% of the people even know that it exists, let alone use it. IMO, searching for book metadata (author, title, possibly "series" or so) would be sufficient for almost everyone. IMO, a full text index is just plain overkill for most people.

But then again, we know how much Amazon listens to customer requests concerning Kindle features.

Aeris · 10-03-2013, 07:20 PM

I've read that someone deleted the Search Indexes directory on Kindle 3 and the indexing stopped... do you think that it is safe to give this a try? (on PW)

All my books are already indexed, it's only a matter of principle xD but I wouldn't like to lose all this work while trying...

ixtab · 10-03-2013, 07:41 PM

You can delete the indexes, but the Kindle will be more than happy to re-generate them on the first occasion. So no, not worth the effort.

Akirainblack · 10-04-2013, 05:10 AM

What about the old trick of deleting the index files, creating folders with the same name and then setting the folder permissions as read only, thereby blocking the indexer?
It's one of the tricks I've read to block background updates.
Just an idea, sorry if it's one that's already been tried and didn't work.

brianinmaine · 10-04-2013, 05:56 AM

Quote:

Originally Posted by Akirainblack

What about the old trick of deleting the index files, creating folders with the same name and then setting the folder permissions as read only, thereby blocking the indexer?
It's one of the tricks I've read to block background updates.
Just an idea, sorry if it's one that's already been tried and didn't work.

Give it a try and let us know - sounds like a great idea to me!

BTW- have you read this one:
https://www.mobileread.com/forums/sho...d.php?t=220735

10-03-2013, 02:33 PM	#1
Aeris Developer's Corner Mascot Posts: 486 Karma: 1277790 Join Date: Sep 2013 Device: Kindle Paperwhite 5.3.4, Kindle Keyboard 3.4	[SOLVED] Indexing wasting all the memory? I gave a glance to /system/Search Indexes/ folder on kindle paperwhite and BAM! Found that it take up 96.8 MB! I've "only" 300 books so it is so pretty annoying that it take so much... Is it safe to delete all these files? Must i keep ones with extensions .db an .lg? Would the database file become corrupted after this operation? Obviously, I need also a way to block the indexer after doing this... I've searched in the forum but didn't find any solution that really works on paperwhite Any idea? Thank you in advance Last edited by Aeris; 10-03-2013 at 02:35 PM.

10-03-2013, 06:23 PM	#8
Aeris Developer's Corner Mascot Posts: 486 Karma: 1277790 Join Date: Sep 2013 Device: Kindle Paperwhite 5.3.4, Kindle Keyboard 3.4	Cover view is sooo cute instead P.S. I've just discovered that the number of pages at the bottom-right is clickable O.O Attached Thumbnails

10-03-2013, 06:40 PM	#10
Aeris Developer's Corner Mascot Posts: 486 Karma: 1277790 Join Date: Sep 2013 Device: Kindle Paperwhite 5.3.4, Kindle Keyboard 3.4	Ohh great, didn't know! Btw, we are a bit off-topic now... if somebody has an idea for stoppin' the fukin' indexer, I'm all ears! Last edited by Aeris; 10-03-2013 at 06:43 PM.*

10-03-2013, 07:20 PM	#12
Aeris Developer's Corner Mascot Posts: 486 Karma: 1277790 Join Date: Sep 2013 Device: Kindle Paperwhite 5.3.4, Kindle Keyboard 3.4	I've read that someone deleted the Search Indexes directory on Kindle 3 and the indexing stopped... do you think that it is safe to give this a try? (on PW) All my books are already indexed, it's only a matter of principle xD but I wouldn't like to lose all this work while trying... Last edited by Aeris; 10-03-2013 at 07:25 PM.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Kindle PW new FW5.3.4 solved PDF low memory	bthoven	Amazon Kindle	6	01-24-2014 06:53 PM
Am I Wasting My Time Requesting Books For The Kindle?	NVash	General Discussions	20	12-12-2010 02:23 AM
Seriously thoughtful "Higher Education: How Colleges are Wasting our Money"	MartinParish	Lounge	29	08-31-2010 10:13 AM
iPad Scribd: Publishers Are Wasting Time, Money, Effort In Creating iPad Apps	kjk	Apple Devices	0	06-11-2010 02:27 PM
SOLVED: How to see the internal memory again	Sunspark	Astak EZReader	19	06-08-2010 11:33 AM

10-03-2013, 03:55 PM	#2
hfpop Addict Posts: 250 Karma: 136662 Join Date: Apr 2011 Device: N/A	Hello, I hate this as well. My solution was, however, different: - forget about indexing; - placed books in /mnt/us/books; - modified kindle explorer to allow ONLY book copy to /mnt/us/documents (modified sources posted in the same thread). In this way my books are NOT indexed. My books are invisible to Kindle. I only make visible books on an as needed basis. I know, this is a solution deserving at most grade 8 on a 1-10 scale. But it is the best I could get so far. If anyone has any ideas on improving this, I am listening.

10-03-2013, 04:11 PM	#3
knc1 Going Viral Posts: 17,212 Karma: 18210809 Join Date: Feb 2012 Location: Central Texas Device: No K1, PW2, KV, KOA	sounds simple and effective. that makes it hard to beat.

10-03-2013, 04:44 PM	#4
Aeris Developer's Corner Mascot Posts: 486 Karma: 1277790 Join Date: Sep 2013 Device: Kindle Paperwhite 5.3.4, Kindle Keyboard 3.4	Don't like it to much... I take ages to put nice covers on my books to have a nice looking library xD Damned indexer...

10-03-2013, 05:56 PM	#5
hfpop Addict Posts: 250 Karma: 136662 Join Date: Apr 2011 Device: N/A	By the way, I have the reversed problem: I want to create books using Calibre, but I want no covers. Without covers, the first image in the book becomes the cover. And I do not want this. My point: I want space for my books, i.e. text, not to look at nice covers. How can I create books with no covers? Thank you

10-03-2013, 06:08 PM	#6
Aeris Developer's Corner Mascot Posts: 486 Karma: 1277790 Join Date: Sep 2013 Device: Kindle Paperwhite 5.3.4, Kindle Keyboard 3.4	FOR ALREADY CONVERTED BOOKS: In Calibre, selects all the book from which you want to remove the cover, right click on them, then Edit metadata -> Edit metadata in bulk -> Change cover -> Remove Cover -> Apply FOR NEW BOOKS: Preferences -> Output options -> No default cover -> Apply

10-03-2013, 06:19 PM	#7
ixtab (offline) Posts: 2,907 Karma: 6736092 Join Date: Dec 2011 Device: K3, K4, K5, KPW, KPW2	Easiest solution: use list view, instead of cover view, on the Kindle . Not only is it less distracting, it's also more compact (it displays 8 books per page instead of 6).

10-03-2013, 06:38 PM	#9
NiLuJe BLAM! Posts: 13,478 Karma: 26012494 Join Date: Jun 2010 Location: Paris, France Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E	@Aeris! It's also contextual (for example, if you're sorting by author, you can jump to authors starting with a specific letter).

10-03-2013, 07:41 PM	#13
ixtab (offline) Posts: 2,907 Karma: 6736092 Join Date: Dec 2011 Device: K3, K4, K5, KPW, KPW2	You can delete the indexes, but the Kindle will be more than happy to re-generate them on the first occasion. So no, not worth the effort.

10-04-2013, 05:10 AM	#14
Akirainblack abibliophobic Posts: 220 Karma: 219708 Join Date: Aug 2012 Device: KV jailbroken	What about the old trick of deleting the index files, creating folders with the same name and then setting the folder permissions as read only, thereby blocking the indexer? It's one of the tricks I've read to block background updates. Just an idea, sorry if it's one that's already been tried and didn't work.

Advert

Advert