Can't find the information you are looking for here? Then leave a message over on our WinBatch Tech Support Forum.
Keywords: tRemoteConn memory
What seems to be happening is that every tRemoteConn to a new server eats up around 300-400Kb of memory. As there does not appear to be a 'close' command to close tRemoteConn connections, I was wondering how best to conserve memory during processing of this type?
My guess is there is some amount of memory loss due to the iniital connection to a new machine. Unfortunately there is not alot we can do about it. It seems to be a problem with the underlying windows API function.
The only suggestion I can make at this point is to have the script process something like 10 servers at a time, then having the script restart itself for the next 10, and exit.
Article ID: W15080
File Created: 2017:07:28:13:58:40
Last Updated: 2002:09:05:13:49:27