I don't know if anybody out there is as nutty as I am, but Everything shows over 27 million items in my Everything database. Using Process Explorer, Everything64.exe is currently showing Private Bytes 4,120,228K, Working Set 4,092,728K, and CPU now 51.35% I have 24GB RAM installed. The CPU is an i5-3570k from 2013.
I don't think the CPU usage is typical, it may be something going on right after the update to 1348a. Now with that CPU usage it's no surprise that things bog down.
I guess there's lots of different things I can do to reduce the RAM usage (if needed) and the CPU cycles, but I haven't done anything yet to deal with my apps being slow to respond.
Anybody else have a database this big?
Huge Database effect on system performance
Re: Huge Database effect on system performance
Thank you for the issue report jimspoon,
Could you please send a mini crash dump when Everything has high CPU usage:
Everything should only have minimal CPU usage while running in the background.I don't think the CPU usage is typical
Could you please send a mini crash dump when Everything has high CPU usage:
- Download Process Explorer from Microsoft:
https://docs.microsoft.com/en-us/sysinternals/downloads/process-explorer - Wait for Everything to have high CPU usage.
- In Process Explorer, select Everything.exe (If there is two, select the one using the most memory)
- Right click Everything64.exe and under Create Dump, select Create Mini Dump.
- Choose a filename and click Save.
- Please send this file to support@voidtools.com
Re: Huge Database effect on system performance
What version of Everything did you have before?
Did you change Everything versions (or did Everything update)? [YES}
Are you indexing "Properties" (in 1.5 alpha)?
If so, the .db structure may change, is in flux, so you might have a re-index going on, which may be long & resource intensive.
(Once that finishes, CPU should be negligible.)
27M & assuming you're indexing at least some Properties, I'd think your 4GB of RAM is in line?
---
Did you change Everything versions (or did Everything update)? [YES}
Are you indexing "Properties" (in 1.5 alpha)?
If so, the .db structure may change, is in flux, so you might have a re-index going on, which may be long & resource intensive.
(Once that finishes, CPU should be negligible.)
27M & assuming you're indexing at least some Properties, I'd think your 4GB of RAM is in line?
---
That's what I have at home, though it looks like I didn't upgrade to that till around 2017.The CPU is an i5-3570k from 2013