limit data usage on a metered connection - scan / indexing / monitoring options

If you are experiencing problems with "Everything", post here for assistance.
Post Reply
gautxori
Posts: 12
Joined: Sat Nov 05, 2016 9:13 am

limit data usage on a metered connection - scan / indexing / monitoring options

Post by gautxori »

Hello,

I use Everything to monitor changes in folders on a local area network when I am connected to the LAN via Ethernet or a VPN with a metered connection.

The metered connection is very slow, and I would like to limit data usage when I connect to it. What settings in Everything should I change to achieve this?

Is it possible to create a command or configuration option in Everything or the Windows command line to automatically limit data usage with these settings when the network connection status changes?
void
Developer
Posts: 19839
Joined: Fri Oct 16, 2009 11:31 pm

Re: limit data usage on a metered connection - scan / indexing / monitoring options

Post by void »

Everything 1.5 has the option to pause indexing.

To pause indexing in Everything 1.5:
  • In Everything 1.5, from the Index menu, check Pause Updates.
To resume indexing:
  • In Everything 1.5, from the Index menu, check Update indexes.


To pause monitors in Everything 1.4:
  • Type in the following search and press ENTER:
    /monitor_pause
To resume monitors in Everything 1.4:
  • Type in the following search and press ENTER:
    /monitor_resume




Everything uses FindFirstFile to index and rescan folders.

Everything uses ReadDirectoryChangesW to monitor changes.

There's no way to reduce the bandwidth of these API calls that I know of..
Check if your VPN has any compression options. -The data for these API calls could be compressed a lot..
Use an SSL tunnel with compression.



Folders under Tools -> Options -> Exclude will not be indexed or rescanned.
Same applies to hidden/system folders if you exclude hidden/system folders under Tools -> Options -> Exclude.
-Everything will still received changes to excluded folders, but they are ignored.
-so excluding doesn't help with monitor changes bandwidth.



Run an ETP server on the server side.
ETP uses very little bandwidth.
Searches are done server side.



Run an Everything Server on the server side.
Searches are done client side.
Client will make a copy of the server index. -The index is compressed when sent to the client.
Monitor changes is very efficient. -Index only filenames (disable size/date-modified indexing) for even less bandwidth.
No rescans necessary -the client will not miss changes on the Everything Server.
Post Reply