RDP Session - Per User RAM

[TheSearchWhisperer]

Dear All,

1st post, go easy (apologies if this has been covered before and I haven't found it).

I love this tool and use it on Windows Servers, I also RDP to those servers and run the tool. So do my team mates. So some large file servers use near 4gb RAM once the index is built. When another RDP session is started then that session will auto start Everything.exe and then also consume near 4gb RAM. So I did a full service install rather than using the portable versions and the same issue still exists.

I would like to achieve one everything.exe process with 1 RAM consumption for all RDP sessions on a server, if possible? I'm open to alternative suggestions if this isn't possible.

Thanks
TheSearchWhisperer

[void]

One way would be to use ETP.

Set up an ETP server as a client service and have your users log in and connect to the ETP Server:

• Copy Everything.exe to an empty folder.
• Make sure no other Everything is running.
• Run this Everything and setup your indexes.
• Setup the ETP server with the desired settings / access
• Set the bind to interfaces to 127.0.0.1 if you only want local machine connections.
• Exit Everything
• Install this Everything as a client service with Everything.exe -install-client-service
• Set your users Everything clients home index to this ETP server:
• From Tools -> Options -> Home, change Index to ETP server
• Change ETP server to 127.0.0.1
• Change link type to C:
• Click OK.

[NotNull]

When another RDP session is started then that session will auto start Everything.exe and then also consume near 4gb RAM.

In another thread (viewtopic.php?f=5&t=6238), someone did a closer inspection on database size in RAM and on disk and came to 42MB RAM for one million files. Those numbers correlate to the numbers I see on my system.

Extrapolating this to your 4GB RAM usage, that would mean 100 million files/folders (!!) that are indexed by Everything.
If you see that there are indeed (about) 100 million objects indexed (left side of the Everything statusbar), there is not much you can do about it, other than excluding "some" folders from being indexed.

[TheSearchWhisperer]

I have tried the ETP suggestion but couldn't get it working.

Did this step> Install this Everything as a client service with Everything.exe -install-client-service
But on this step > Set your users Everything clients home index to this ETP server -------> Which everything.exe do you run?

I tried running the Exe used for the client service but that's no good as that is set to ETP server on localhost.

I put another 32bit portable version in a different folder and ran that but it wouldn't bring up the gui and when it did, would crash.

Maybe I'm doing something wrong?
Using ECP remotely is a good work-around though. But if my teammates don't remember to do it that way then it will be the same as before so would prefer to get it going on localhost.

Does that make sense?

Thanks
TSW

[NotNull]

Does this work for you? :

- Create a shortcut to the "server" Everything.exe with this command-line parameters:

Code: Select all

drive:\path\to\Everything.exe -instance "%USERNAME%" -connect ETP-username:ETP-Password@localhost:ETP-Port -drive-links -nodb

example: C:\BIN\Everything\Everything.exe -instance "%USERNAME%" -connect randomname:secret@localhost:21 -drive-links -nodb

Start this shortcut.
Every user gets it's own INI file (Everything-username.ini; will be created on the fly), so each person can have their individual settings.

[NotNull]

I missed this one upon first reading:

I put another 32bit portable version in a different folder and ran that but it wouldn't bring up the gui and when it did, would crash.

Please don't use the 32-bit version of Everything for this. 32-bit programs can only address 2 GB of memory (theoretically up to 4GB with some "trickery", but in reality way less). That's asking for trouble with your 4GB database ...

[TheSearchWhisperer]

Sorry for the massive delay in responding.

Just had another go at this, making sure I used the same x64 bit exe (not x86) that I used to install the service and creating the shortcut using the right syntax. It now works and achieves exactly what I wanted.

Thanks very much for your help.