Resources for ScreenConnect on CentOS 7
-
@gjacobse said in Resources for ScreenConnect on CentOS 7:
From the conversations I had with SC on the matter,... it seems that the Client Agent chatter (calling home, checking updating version) can cause the system to be 'laggy'... but once done, it'll quiet down.
@scottalanmiller would know on this.
How long does it take for things to quiet down?
-
@Dashrender said in Resources for ScreenConnect on CentOS 7:
@gjacobse said in Resources for ScreenConnect on CentOS 7:
From the conversations I had with SC on the matter,... it seems that the Client Agent chatter (calling home, checking updating version) can cause the system to be 'laggy'... but once done, it'll quiet down.
@scottalanmiller would know on this.
How long does it take for things to quiet down?
@JaredBusch said in Resources for ScreenConnect on CentOS 7:
2 minutes and 40 seconds before it stabilized.
About 3 minutes.
-
-
After 10 minutes, it has been sitting unchanged with the memory usage. CPU spikes to 100% a few times that I noticed.
I intentionally used 4GB here to make sure nothing should feel the need to go to swap.
[root@bnasc ~]# free -m total used free shared buff/cache available Mem: 3760 1293 1959 8 506 2214 Swap: 1791 0 1791 [root@bnasc ~]# -
At 2GB, we never see it need it all. It's decently lean.
-
@scottalanmiller said in Resources for ScreenConnect on CentOS 7:
At 2GB, we never see it need it all. It's decently lean.
Been watching things and it seems to need another CPU. Everytime I click on something on the webpage, the CPU spikes to 100%.
-
@JaredBusch said in Resources for ScreenConnect on CentOS 7:
@scottalanmiller said in Resources for ScreenConnect on CentOS 7:
At 2GB, we never see it need it all. It's decently lean.
Been watching things and it seems to need another CPU. Everytime I click on something on the webpage, the CPU spikes to 100%.
I think that we use two.
-
@scottalanmiller said in Resources for ScreenConnect on CentOS 7:
@JaredBusch said in Resources for ScreenConnect on CentOS 7:
@scottalanmiller said in Resources for ScreenConnect on CentOS 7:
At 2GB, we never see it need it all. It's decently lean.
Been watching things and it seems to need another CPU. Everytime I click on something on the webpage, the CPU spikes to 100%.
I think that we use two.
Since we are having issue with our system
$ sysctl vm.swappiness vm.swappiness = 30 -
@gjacobse said in Resources for ScreenConnect on CentOS 7:
@scottalanmiller said in Resources for ScreenConnect on CentOS 7:
@JaredBusch said in Resources for ScreenConnect on CentOS 7:
@scottalanmiller said in Resources for ScreenConnect on CentOS 7:
At 2GB, we never see it need it all. It's decently lean.
Been watching things and it seems to need another CPU. Everytime I click on something on the webpage, the CPU spikes to 100%.
I think that we use two.
Since we are having issue with our system
$ sysctl vm.swappiness vm.swappiness = 30Why not go lower to say... 10 ?
-
@dafyre said in Resources for ScreenConnect on CentOS 7:
@gjacobse said in Resources for ScreenConnect on CentOS 7:
@scottalanmiller said in Resources for ScreenConnect on CentOS 7:
@JaredBusch said in Resources for ScreenConnect on CentOS 7:
@scottalanmiller said in Resources for ScreenConnect on CentOS 7:
At 2GB, we never see it need it all. It's decently lean.
Been watching things and it seems to need another CPU. Everytime I click on something on the webpage, the CPU spikes to 100%.
I think that we use two.
Since we are having issue with our system
$ sysctl vm.swappiness vm.swappiness = 30Why not go lower to say... 10 ?
-
@dafyre said in Resources for ScreenConnect on CentOS 7:
@gjacobse said in Resources for ScreenConnect on CentOS 7:
@scottalanmiller said in Resources for ScreenConnect on CentOS 7:
@JaredBusch said in Resources for ScreenConnect on CentOS 7:
@scottalanmiller said in Resources for ScreenConnect on CentOS 7:
At 2GB, we never see it need it all. It's decently lean.
Been watching things and it seems to need another CPU. Everytime I click on something on the webpage, the CPU spikes to 100%.
I think that we use two.
Since we are having issue with our system
$ sysctl vm.swappiness vm.swappiness = 30Why not go lower to say... 10 ?
That's what I set them to
-
@scottalanmiller said in Resources for ScreenConnect on CentOS 7:
@dafyre said in Resources for ScreenConnect on CentOS 7:
@gjacobse said in Resources for ScreenConnect on CentOS 7:
@scottalanmiller said in Resources for ScreenConnect on CentOS 7:
@JaredBusch said in Resources for ScreenConnect on CentOS 7:
@scottalanmiller said in Resources for ScreenConnect on CentOS 7:
At 2GB, we never see it need it all. It's decently lean.
Been watching things and it seems to need another CPU. Everytime I click on something on the webpage, the CPU spikes to 100%.
I think that we use two.
Since we are having issue with our system
$ sysctl vm.swappiness vm.swappiness = 30Why not go lower to say... 10 ?
That's what I set them to
Just checked - It's 30...
$ uptime 17:48:06 up 1 day, 3:02, 2 users, load average: 0.00, 0.04, 0.07 $ sysctl vm.swappiness vm.swappiness = 30 ~~
