Re-indexing Everything instead of 27 htmls?

[Biff]

I added this

;I:\Eigene Dateien\Chat\**.html

to the "Include only files" field in "Content" to other folders / paths already existing there with files to be indexed.

The folder "Chat" contains 27 html files from 550 kb of size up to 4,5 MB.

It seems as if Everything did the complete indexing (started at 37 % near the green bar) of all the files already indexed again, instead of only the indexing of the new 27 htmls.

Is there a way to avoid that and let it index only the new (27) files?

[Herkules97]

I added this

;I:\Eigene Dateien\Chat\**.html

to the "Include only files" field in "Content" to other folders / paths already existing there with files to be indexed.

The folder "Chat" contains 27 html files from 550 kb of size up to 4,5 MB.

It seems as if Everything did the complete indexing (started at 37 % near the green bar) of all the files already indexed again, instead of only the indexing of the new 27 htmls.

Is there a way to avoid that and let it index only the new (27) files?

You are sure it actually re-indexed all files or at least much more than 27?
In my experience, EBV might re-do some scans when adding new stuff but most of the indexed data is kept. 99%-ish.

This is very evident with my largest instance that isn't indexing properly over time. It just stops when I have the 4 extra properties I want indexed on it and requires a restart to resume indexing those extra properties.
Anyway..If I take too long to start the instance after exiting it, it will cause a re-build because too much changed since last exit. After this re-build, it still has all the existing extra properties indexed and there is no way it re-scanned every single file again. I would hear the HDDs work if that was the case and also it would take several days. A re-build can take several minutes.
So if that instance has all properties indexed for 10mil files, it will still have those indexed upon a re-build and because it would take days if not weeks to actually re-scan properties for those 10mil files it couldn't have happened in the few minutes of the re-building.

And when adding new properties, old properties are also still kept. If all files had "Size on disk" indexed and I add CRC-64, they will still have size on disk when it gets done re-building. Or at least 99% of them will, relatively minor losses if there are any.

[Biff]

You are sure it actually re-indexed all files or at least much more than 27?

No no, I am not at all, it seemed as if, but maybe or probably it is not like that. In any case it lasts very long.

What is EBV?

OK, I am not quite sure yet what that means for the behavior above.

[Herkules97]

You are sure it actually re-indexed all files or at least much more than 27?

No no, I am not at all, it seemed as if, but maybe or probably it is not like that. In any case it lasts very long.

Don't know what "very long" means.

What is EBV?

This program, Everything by Voidtools.

OK, I am not quite sure yet what that means for the behavior above.

If I understand what you are doing correctly, you will run into these every time you add more files or folders via the include file thing.
Didn't know anyone used EBV this way, I think 99% of users use the NTFS or otherwise device monitoring.

Maybe if you have 8GB of RAM but still want the full basic properties you might want to index specific files.
I would still run another instance whose sole purpose is having the entire device indexed in the most basic form. I think about 2.4mil files/folders without any properties checked in options was 100MB RAM or so..Let's say 200MB. The first file created was 47MB or so. So around 100MB-200MB RAM, 42-47MB space on disk.
It would mean always having access to an index, even if another one is currently being re-built.

The basic properties may be fast enough that you can run an index with only name and path, and then still keep the other columns active.
When columns are active, EBV tries to read them.
I don't think RAM is big doing it this way..But it does mean it has to re-read the properties every time you search or at least more than if you properly saved them.

[Biff]

Don't know what "very long" means.

So to say the opposite of "very short".

Ah, EBV (not EbV?), extremely cool. WUIM!

If I understand what you are doing correctly, you will run into these every time you add more files or folders via the include file thing.
Didn't know anyone used EBV this way, I think 99% of users use the NTFS or otherwise device monitoring.

I am not quite sure, you mean, each time I do the similar / same, the reindex will be as long? And only 1 % of users use content indexing?

Maybe if you have 8GB of RAM but still want the full basic properties you might want to index specific files.

Yes, that is what I do. I have 14 GB RAM.

I would still run another instance whose sole purpose is having the entire device indexed in the most basic form.

Why?

It would mean always having access to an index, even if another one is currently being re-built.

I am not quite sure, if I understand correctly, but one can use Everything (search) while Everything is indexing, so actually that does not matter in this regard, I would think. But yes, such a basic instance is a good idea.

[Herkules97]

So to say the opposite of "very short".

Hue hue.

I am not quite sure, you mean, each time I do the similar / same, the reindex will be as long? And only 1 % of users use content indexing?

This has been my mistake, I think I ignored the "content" indexing part of the OP.
I thought you were just adding individual folders to be indexed altogether.

Well the answer remains the same, you can't avoid the re-building if you add folders at least as far as I know which may not be the complete picture, Void would know.
Any time you add new stuff to the index, it will re-build.

I am not familiar enough with file content indexing to know why it would re-index existing content, if that is what it does.
Given that I don't know what "very long" means, maybe your understanding of it is actually the expected amount of time for the files you are content-indexing.
I only use file content indexing for ONE instance, it is folder monitor only and is seldom on and I've never added more to it after initially adding file content indexing because I have nothing more to add to it.
I don't content-index outside of it, the few times I need to see inside files I use Agent Ransack.

If you are just adding files randomly all over the place for content indexing, you would benefit from placing the files you want content-indexed into one folder and only content-index that folder as that would prevent EBV from having new stuff added to it and thus no more re-builds/re-indexes until a system failure.

[Biff]

Well the answer remains the same, you can't avoid the re-building if you add folders at least as far as I know which may not be the complete picture, Void would know.
Any time you add new stuff to the index, it will re-build.

Well, well, yes, rebuilding / including the new files in the index sounds plausible, but I'm wondering why it's apparently reindexing files that are already being indexed.

This is all very confusing for my low activity brain. But right now, it seems like whatever gets indexed and reindexed gets indexed and reindexed, for whatever reason.

Okey, many thanks for your great help!

[Herkules97]

Well the answer remains the same, you can't avoid the re-building if you add folders at least as far as I know which may not be the complete picture, Void would know.
Any time you add new stuff to the index, it will re-build.

Well, well, yes, rebuilding / including the new files in the index sounds plausible, but I'm wondering why it's apparently reindexing files that are already being indexed.

This is all very confusing for my low activity brain. But right now, it seems like whatever gets indexed and reindexed gets indexed and reindexed, for whatever reason.

Okey, many thanks for your great help!

The best thing I can think of is that you hover over the progress bar to see what it actually indexes.
After it is done re-building, it will move on to indexing properties and say each file.
If you only have 27 new files and it isn't actually content-indexing old files you should be able to count each individual file while hovering over the progress bar.

Another method could be to click through the drop-downs at the top.
Tools -> Debug -> Statistics will tell you some stats.
I do not know if any of them would tell you the stats for the indexing part.
If all you add are 27 new files, no folders, then maybe one of them could say 27 at the end and that would confirm it.
Or none of them tells the indexing count.

[Biff]

OK, good ideas. I will try to find out the next time adding a new entry to the "Include only files". In the statistics I cannot find anything in this regard.

Many thanks!

[therube]

Is there a way to avoid that and let it index only the new (27) files?

Related (& of which I'm going to have to come back to - at some point), Anyway to prevent intermittent indexing, or to back up the index so it doesn't have to be completely rebuilt?

[Biff]

Ah, yes, thank you for the link!

OK, so I am looking forward to you coming back, many thanks!