Support • Re: 使用过程中未响应问题

检查任务管理器。
在“详细信息”选项卡下，查看工作集（内存）和提交大小。
工作集（内存）= RAM 中的内存。
提交大小 = Everything 请求的内存。
工作集的大小应与提交大小大致相同。
如果 Everything 正在从磁盘分页，则工作集应该会增加。

Everything 可能正在忙于处理更改。
请尝试按修改日期排序，以查看是否有东西在向文件系统发送更改。

Everything 1.5 有 索引日志。
Everything 1.5 可以锁定物理 RAM 中的内存：

• 在 Everything 1.5 中，从 工具 菜单单击 选项。
• 单击左侧的高级选项卡。
• 在显示包含的设置的右侧，搜索：
  lock
• 选择：virtual_lock
• 将值设置为：true
  
• 在显示包含的设置的右侧，搜索：
  working
• 选择：min_working_set_size
• 将值设置为：3758096384
  (3.5GB)
• 选择：max_working_set_size
• 将值设置为：3758096384
  (3.5GB)
• 单击确定。

在内存不足的情况下，Everything 可能仍会被分页到磁盘。

Physical memory 64G, the number of files is indeed quite large
The current Everything.db file is about 5G, the index content only leaves the file name, and the rest is removed
The Everything process occupies about 3G in memory
If it is not used for a period of time, the whiteboard will not respond when searching again, and it will take a long time to load the database after restarting
I wonder if it is a virtual memory problem that causes the memory data to be written back to the virtual memory area of ​​the hard disk when it is not used for a long time, so it is stuck. How to confirm it?

Check the Task Manager.
Under the Details tab, look at the working set (memory) and commit size.
working set (memory) = memory in RAM.
commit size = memory requested by Everything.
working set should be around the same size as the commit size.
working set should be increasing if Everything is being paged from disk.

Everything could be busy processing changes.
Please try sorting by date modified to see if something is spamming your file system with changes.



Everything 1.5 has the index journal.
Everything 1.5 can lock memory in physical RAM:

• In Everything 1.5, from the Tools menu, click Options.
• Click the Advanced tab on the left.
• To the right of Show settings containing, search for:
  lock
• Select: virtual_lock
• Set the value to: true
  
• To the right of Show settings containing, search for:
  working
• Select: min_working_set_size
• Set the value to: 3758096384
  (3.5GB)
• Select: max_working_set_size
• Set the value to: 3758096384
  (3.5GB)
• Click OK.

Everything may still be paged to disk in low memory situations.

Statistics: Posted by void — Mon Nov 25, 2024 8:07 am

---