Hi,
Since indexing the content is an amazing job, I am OK to see Everything index and I am OK with PC being slow during that time. But, even if Everything is not indexing (not showing at the bottom right corner), it still uses huge disk process. Of course I have taken the screenshot from a peak point, but compared to the stable version of Everything, the alpha version is always close to the top.
Disk Usage
-
nesedenyana
- Posts: 58
- Joined: Mon Sep 19, 2022 10:38 am
Disk Usage
- Attachments
-
- Screenshot-20221227-1404.png (226.69 KiB) Viewed 1450 times
Re: Disk Usage
The content you index has to go somewhere. A database is created, loaded into ram and stored for later reference. This will make searching for content faster at the expense of utilizing more computer resources.
If you need to purchase additional ram or hard disk space, these are not terribly difficult to upgrade. If you are on a budget, you can selectively limit the exact files that you wish to content-index, or you can disable content indexing all together until additional computer hardware funds become available.
400 megabytes isn't much to ask for content indexing. Another fellow was inquiring about 3 gigabytes being used after indexing all of his documents. The more documents, large documents... the larger the database.
If you need to purchase additional ram or hard disk space, these are not terribly difficult to upgrade. If you are on a budget, you can selectively limit the exact files that you wish to content-index, or you can disable content indexing all together until additional computer hardware funds become available.
400 megabytes isn't much to ask for content indexing. Another fellow was inquiring about 3 gigabytes being used after indexing all of his documents. The more documents, large documents... the larger the database.
-
nesedenyana
- Posts: 58
- Joined: Mon Sep 19, 2022 10:38 am
Re: Disk Usage
What do you mean by loaded into ram? Isn't this like a database that we reach when we use the content search? As you can see I am not doing any content search at the moment of screenshot. Also, I was talking about disk usage, not the ram usage.
Re: Disk Usage
Everything keeps its database in memory - it only writes it to disk periodically so that it can read it when it starts up to avoid having to re-index at startup.
Once you index content, Everything keeps the results in memory, whether you are searching it or not.
Once you index content, Everything keeps the results in memory, whether you are searching it or not.
Re: Disk Usage
(I am aware the following is a bit vague, but that is the best I can do at the moment frommemory)
The status of the initial indexing of file content will be shown in the statusbar.
IIRC, Subsequently updates of this index will be done in the background and will not be shown in the statusbar.
My guess is that Everything is indeed updating content as the the disk activity you are seeing is very a-typical for Everything when "idling".
To check, go to menu:Tools => Options => Indexes => Content tab.
In the upper right corner the current file/folder that is being indexed will be shown.
If you wait for a couple of minutes, does the disk activity go back to zero?
FWIW: Everything can be aggressive when indexing local SSD content, as it tries to use as many threads as possible to "get over it ASAP". The number of threads that are used can be configured. This means the disk will be less taxed, at the price of longer processing time.
The status of the initial indexing of file content will be shown in the statusbar.
IIRC, Subsequently updates of this index will be done in the background and will not be shown in the statusbar.
My guess is that Everything is indeed updating content as the the disk activity you are seeing is very a-typical for Everything when "idling".
To check, go to menu:Tools => Options => Indexes => Content tab.
In the upper right corner the current file/folder that is being indexed will be shown.
If you wait for a couple of minutes, does the disk activity go back to zero?
FWIW: Everything can be aggressive when indexing local SSD content, as it tries to use as many threads as possible to "get over it ASAP". The number of threads that are used can be configured. This means the disk will be less taxed, at the price of longer processing time.