Running as service vs. administrator

[Coldblackice]

If using a Windows administrator account full-time, are there any pros/cons to using Everything as a service vs. run-as administrator?

[void]

If you are already running as administrator there is no need to install the Everything service. It will literally do nothing, as Everything will just read the USN journals on NTFS volumes directly. The Everything service uses about 1MB of ram.

If you are using a standard user account then there's no efficiency or performance difference between running the Everything service or running Everything as administrator. When using the Everything service there's no UAC prompts and applications run from Everything run as a standard user.

For more information please see:
Everything Service Help

[Coldblackice]

Thanks. Which do you personally use -- administrator or service?

Aside from performance differences, which you say there are none, and besides UAC warnings, are there any other particulars of services that might be a pro or con? For example, I know services typically start up before Windows login -- would this be useful for Everything, to start indexing earlier (or could it be non-ideal to start so early in boot)?

[void]

I use the true administrator account, but I don't recommend you use that.

The service is stateless, the service doesn't manage the database, its just a wrapper to read USN Journals on NTFS volumes. Windows will start the service before the everything search window is created. The service can't be used to load the database earlier.

There might be some overhead with the service using sockets, but it shouldn't be noticeable.