Just starting to test the Server/Network Index option. working great so far. Learning the nuances. Goal would be to have every user on an RDS host be able to launch Everything and search across network. It appears that each instance launched is eating up about 800MB of memory. There are about 8 million files its displaying and reports about 7TB's of data. The Everything-1.5a.db is showing about 400MB on the file server.
Are there any tips to lessen the memory usage per user? or does it just depend on the amount of files being displayed?
Memory usage - normal?
Re: Memory usage - normal?
75-100MB per 1 million files is what is to be expected.
The Everything Server 'broadcasts' all changes it finds to the clients, to be loaded in the client databases.
Each user builds it's own database (and loads it in memory).
If you want your users just to index network shares (no local files/folders), you might want to consider installing an ETP Server instead.
The ETP Server is true client/server: ETP clients connect to the ETP Server. The search query is sent to the ETP Server, the ETP Server checks it's database and reports *just* the results back to the ckleint. The client shows them on screen.
This means minimal memory (RAM) usage on the client (couple of MB).
See also optimal settings for Everything 1.4 to shave off a little bit of memory at the price of minor functionality loss.
The Everything Server 'broadcasts' all changes it finds to the clients, to be loaded in the client databases.
Each user builds it's own database (and loads it in memory).
If you want your users just to index network shares (no local files/folders), you might want to consider installing an ETP Server instead.
The ETP Server is true client/server: ETP clients connect to the ETP Server. The search query is sent to the ETP Server, the ETP Server checks it's database and reports *just* the results back to the ckleint. The client shows them on screen.
This means minimal memory (RAM) usage on the client (couple of MB).
See also optimal settings for Everything 1.4 to shave off a little bit of memory at the price of minor functionality loss.
Re: Memory usage - normal?
Thank you for the ETP suggestion. I'm testing it out right now. I am seeing very small memory usage (like 3-5MB) which is great.. and its very zippy. Question on the shares.. does it honor windows file rights for the "search" too? It looks like you can only point to one ETP server, vs the Everything Server you could have multiple.
If I put all my files on FILESERVER2 but have subfolders.. drive E:.. then an HR subfolder.. and "Clients" folder. Can the HR folder be restricted by NTFS persmissions for only those who have rights to see those files? My assumption is Everything will show all available files to the clients, but wont let them open it what they cant access.. but in this example, I wouldnt want them to see the HR file names either.
Also, is there a way for the client to auto-connect to ETP server on launch?
Hope that makes sense
If I put all my files on FILESERVER2 but have subfolders.. drive E:.. then an HR subfolder.. and "Clients" folder. Can the HR folder be restricted by NTFS persmissions for only those who have rights to see those files? My assumption is Everything will show all available files to the clients, but wont let them open it what they cant access.. but in this example, I wouldnt want them to see the HR file names either.
Also, is there a way for the client to auto-connect to ETP server on launch?
Hope that makes sense
Re: Memory usage - normal?
No, what you index is what is visible to the Everything client.does it honor windows file rights for the "search" too?
ETP is designed for a single user account.
edit: changed "single user" to "single user account".
Correct, you can only connect to one ETP server.It looks like you can only point to one ETP server, vs the Everything Server you could have multiple.
You cannot index an ETP server at this stage.
What the ETP server indexes is what the ETP client sees.If I put all my files on FILESERVER2 but have subfolders.. drive E:.. then an HR subfolder.. and "Clients" folder. Can the HR folder be restricted by NTFS persmissions for only those who have rights to see those files?
Correct.My assumption is Everything will show all available files to the clients, but wont let them open it what they cant access..
ETP client will list the files.
The windows shares will be inaccessible.
Please make sure you turn off allow file download under Tools -> Options -> ETP -> Allow File download.
Otherwise these files could be downloaded over FTP.
Please try setting the home index under Tools -> Options -> Home -> Index -> ETP Server.Also, is there a way for the client to auto-connect to ETP server on launch?
-or-
Use the -connect command line option.
Re: Memory usage - normal?
Ugh 
lol both options are great but have unique cons.
Curious, what happens if you run ETP server with multiple clients pointed at it? I understand its intended for 1 user..
Everything Server would be perfect if it behaved a bit like ETP server (ish) and the server handled the heavy lifting (in my situation where everyone is WFH and using an RDS host). The ability to have multiple network indexes/servers, etc is awesome!
ETP server also great (very fast, low memory usage).
lol both options are great but have unique cons. Curious, what happens if you run ETP server with multiple clients pointed at it? I understand its intended for 1 user..
Everything Server would be perfect if it behaved a bit like ETP server (ish) and the server handled the heavy lifting (in my situation where everyone is WFH and using an RDS host). The ability to have multiple network indexes/servers, etc is awesome!
ETP server also great (very fast, low memory usage).
Re: Memory usage - normal?
Thank you for your feedback joebrug,
You can have as many users as you like (< 10000).
I should have said one user account.Curious, what happens if you run ETP server with multiple clients pointed at it? I understand its intended for 1 user..
You can have as many users as you like (< 10000).