Announcement

Collapse
No announcement yet.

(Testing) a virgin Linux HS3 v. 531 on a vm I just created (Ubuntu 19.04)

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • (Testing) a virgin Linux HS3 v. 531 on a vm I just created (Ubuntu 19.04)

    Some folks here reports that hs3 has a memory leak. As a starting point I wanted to see how hs3 consume memory in a virgin state. Mono stable is installed ( 5.20.1.19)

    HS3 is configured to start as a service.

    1.First picture is when I start the vm.

    2.Second picture, is a little after. I open all the menus i can think off on the web interface. That makes the memory jumps to 114m. I make that to be sure that all what a user could press on is loaded in memory.

    3.Third one I repeat the same process as #2, 10 minutes after. No real effect.

    4. wait 10-15 minutes , doing nothing. 121m

    5. Wait another 15 mins . Memory still in the same range . 122m.

    Attached Files

  • #2
    Just created 5 virtual device with theses two event.

    So every 5 sec, the devices change from off to on.

    Did NOT disable any logs.

    Will let this run for the night.


    -Memory is still the same. 123m.


    -Ten minutes after. memory is at 128m.

    -Another 10 mins. Memory went back to 120m. I think we have a baseline here.


    Attached Files

    Comment


    • #3
      Good news MattLO!!

      I have not seen any HS3 memory leaks running Homeseer 3 Pro or Lite V531 on Ubuntu 18.04 64 bit.

      - Pete

      Auto mator
      Homeseer 3 Pro - 3.0.0.534 (Linux) - Ubuntu 18.04/W7e 64 bit Intel Haswell CPU - Mono 6.00
      Homeseer Zee2 (Lite) - 3.0.0.534 (Linux) - Ubuntu 18.04/W7e - CherryTrail x5-Z8350 BeeLink 4Gb BT3 Pro - Mono 6.00

      X10, UPB, Zigbee, ZWave and Wifi MQTT automation.

      Comment


      • #4
        -here after 12 hours . memory is at 135m.

        -35 min after that . still at 135m

        -another 20 min after still at 135m.

        Will report back tomorrow
        Attached Files

        Comment


        • #5
          Originally posted by Pete View Post
          Good news MattLO!!

          I have not seen any HS3 memory leaks running Homeseer 3 Pro or Lite V531 on Ubuntu 18.04 64 bit.
          Mine s leaking. This is why i do this test. Will continue for 5-7 days if i can.

          Comment


          • #6
            -after another 24 hours . 147m
            -25 min after that still at 147m
            -25 min after that still at 147m
            Attached Files

            Comment


            • #7
              -24 hours later . 169m
              2h after that . 165m
              Attached Files

              Comment


              • #8
                -24 hours later . Still at 168m.

                -2 hours later same usage. 166m

                IIt is hard to standardize this test... But i think We can conclude that there is no leak with hs3 running Linux.

                Since we have a baseline with no leak..I will install all the plugin I use, and see if there is a leak .
                Installing plugin cause a memory rise ( If we can call this a leak ) .. so the memory will be higher after all the plugin installation.

                But we'll get a baseline and start from here.
                Attached Files

                Comment


                • #9
                  If you want to keep a record over time, use vmstat command. For example,

                  vmstat 60

                  runs every 60 seconds.

                  Comment


                  • #10
                    Thanks zwolfpack. Is there any way to monitor a particular process?

                    I think i'll just send the values to mqtt and monitor with node-red ( as I did on my real hs3 server), so I'll get a graph of the memory used by hs3 process.


                    Comment


                    • #11
                      Thinking about it, vmstat isn't such a good fit, as it monitors the entire machine, not just a single process. Instead, you could use top, with options to monitor just one process and in "batch" mode

                      top -b -p 937 -d 300

                      where 937 is the process id you want to monitor and 300 is number of seconds per update.

                      To filter out some extraneous stuff,

                      top -b -p 937 -d 300 | egrep "^top|mono"

                      will only pass lines starting with "top" and containing "mono"; this will show the time and the process info.

                      Comment


                      • #12
                        Originally posted by zwolfpack View Post
                        Thinking about it, vmstat isn't such a good fit, as it monitors the entire machine, not just a single process. Instead, you could use top, with options to monitor just one process and in "batch" mode

                        top -b -p 937 -d 300

                        where 937 is the process id you want to monitor and 300 is number of seconds per update.

                        To filter out some extraneous stuff,

                        top -b -p 937 -d 300 | egrep "^top|mono"

                        will only pass lines starting with "top" and containing "mono"; this will show the time and the process info.
                        thanks !

                        Comment


                        • #13
                          as i said . installing all those plugin was going to skyrocket hs3 memory usage.

                          -So 318m.

                          will run the command from Zwolfpack 1-2 hours from now.
                          The problem here is the system is doing almost nothing.
                          If memory is stable again.. I will transfer my install into the vm



                          Attached Files

                          Comment


                          • #14
                            seems stable to me . 318m

                            will chek again tomorrow<

                            top -b -p 937 -d 300 | egrep "^ PID|mai"


                            PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
                            937 root 20 0 2513100 329160 39932 S 6,2 4,3 76:49.94 (System)_22-mai
                            PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
                            937 root 20 0 2506940 322516 39932 S 10,1 4,2 77:20.27 (System)_22-mai
                            PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
                            937 root 20 0 2503880 319268 39932 S 10,1 4,2 77:50.60 (System)_22-mai
                            PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
                            937 root 20 0 2504892 320216 39932 S 10,1 4,2 78:20.95 (System)_22-mai
                            PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
                            937 root 20 0 2509004 324836 39932 S 10,1 4,3 78:51.28 (System)_22-mai
                            PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
                            937 root 20 0 2503884 319668 39932 S 10,1 4,2 79:21.64 (System)_22-mai
                            PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
                            937 root 20 0 2503864 319120 39932 S 10,1 4,2 79:51.96 (System)_22-mai
                            PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
                            937 root 20 0 2512076 326468 39932 S 10,3 4,3 80:22.91 (System)_22-mai
                            PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
                            937 root 20 0 2504904 320180 39932 S 10,2 4,2 80:53.44 (System)_22-mai
                            PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
                            937 root 20 0 2503864 319312 39932 S 10,1 4,2 81:23.80 (System)_22-mai
                            PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
                            937 root 20 0 2512040 327128 39932 S 10,1 4,3 81:54.24 (System)_22-mai
                            PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
                            937 root 20 0 2506924 322060 39932 S 10,1 4,2 82:24.49 (System)_22-mai
                            PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
                            937 root 20 0 2503852 319140 39932 S 10,1 4,2 82:54.93 (System)_22-mai
                            PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
                            937 root 20 0 2513068 327944 39932 S 10,2 4,3 83:25.43 (System)_22-mai
                            PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
                            937 root 20 0 2506924 321756 39932 S 10,2 4,2 83:55.96 (System)_22-mai
                            PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND

                            Comment


                            • #15
                              -24 h later 333m
                              Attached Files

                              Comment

                              Working...
                              X