NikkoSuave
Member
Hello All,
Currently programming the HMI for a project. We are using a server that hosts 13 different virtual machines. 3 terminal servers, 3 HMI project servers, 3 alarms servers, one database server...etc. 60 HMI clients that remote desktop in to one of the terminal servers and runs the Factory talk client on there.
I have noticed that there is a process that belongs to factory talk client called "SAUserServ Module". I have noticed this process begins to consume more and more memory until it used too much, Ive seen in climb as high as 300 MB on the weekend.
Does anyone know what this process is exactly for? Maybe it would help me pinpoint the reason for the memory consumption. These HMI's will need to run mostly maintenance free 24/7. So deleting the process every few days is not an option.
I have been using factory talk view se for almost a year and have came to the conclusion it is the most buggiest, poorly documented piece of software I have ever used.
Thanks for any help.
Currently programming the HMI for a project. We are using a server that hosts 13 different virtual machines. 3 terminal servers, 3 HMI project servers, 3 alarms servers, one database server...etc. 60 HMI clients that remote desktop in to one of the terminal servers and runs the Factory talk client on there.
I have noticed that there is a process that belongs to factory talk client called "SAUserServ Module". I have noticed this process begins to consume more and more memory until it used too much, Ive seen in climb as high as 300 MB on the weekend.
Does anyone know what this process is exactly for? Maybe it would help me pinpoint the reason for the memory consumption. These HMI's will need to run mostly maintenance free 24/7. So deleting the process every few days is not an option.
I have been using factory talk view se for almost a year and have came to the conclusion it is the most buggiest, poorly documented piece of software I have ever used.
Thanks for any help.
