1 Reply Latest reply on Jun 10, 2013 6:37 PM by dans

    McAfee Move mvadm status explanation?

    dans

      Can someone give me a little help on how to read the performance stats of McAfee MOVE's mvadm command?

       

      The output of mvadm status:

       

      C:\Program Files (x86)\McAfee\MOVE AV Server>mvadm.exe status

      Total number of cksum req:                6629518

      Total number of file transfer req:        5553596

      Total number of smart file req:              6779

      Cksum cache hit:                          1075915

      Total av scan req:                        5553586

      Total av scan failure:                          0

      Data recv failure:                             11

      Resp send failure:                             25

      Total scan threads:                           300

      Total heart beat threads:                      56

      Total idle threads:                           295

      Number of requests in queue:                    0

      Number of items in cache:                  999756

      Avg request process time:                0.148097 sec

      Avg request wait time:                   0.000030 sec

       

      Question 1) I'm looking at Total number of checksum requests at 6.5 million and a cache hit of 1 million. That's a pretty low cache hit of around 15%. Is this considered a good number? Is there a way to improve it?

       

      Question 2) Total number of file transfer requests. Can someone explain what this is? Is this saying that all of my MOVE clients have made a total of 5,553,596 requests of files not in the clients local checksum cache? How can I improve this number? I suspect that would improve performance tremendously since the client would have the answer locally vs. over the network?

       

      Question 3) Number of items in the chace are 999,756. My configuration says to MaxCacheItems        1,000,000 (0xf4240). That means I've basically maxed my cache. Comparing that with my curent cache hit of 15% it seems I'll probably continue getting a 15% cache hit. Also, how does the cache clear itself? Is it first-in first-out or something smarter such as how often the item in cache is used?

       

      Any other advice on how to read these stats to communicate to the applications team how McAfee Move is performing....or not performing and how I can scale and improve my deployment as we deploy this to a  larger scale.

       

       

      Thanks for any help,

      Daniel

        • 1. Re: McAfee Move mvadm status explanation?
          dans

          To add to the fun, here's another MOVE server in my environment:

           

          C:\Program Files (x86)\McAfee\MOVE AV Server>mvadm stats

          Total number of cksum req:               20340430

          Total number of file transfer req:        9765489

          Total number of smart file req:             89429

          Cksum cache hit:                         10574458

          Total av scan req:                        9765486

          Total av scan failure:                          0

          Data recv failure:                            484

          Resp send failure:                            156

          Total scan threads:                           300

          Total heart beat threads:                      56

          Total idle threads:                           299

          Number of requests in queue:                    0

          Number of items in cache:                  109905

          Avg request process time:                0.125048 sec

          Avg request wait time:                   0.000012 sec

           

          Q1) chskum hits vs. total requests - Total requests 20 million. Total cache hit 10.5 million. Almost getting 50% hit rate on this one?

          Q2) 9.7 million file transfer requests? No idea what this means

          Q3) 109,905 items in cache? That's insanely less than what we see on the first MOVE server above, which is at nearly 1 million max items. Maybe I don't understand what this is saying either.

           

          Q4) New question - What are smart file reqests?

          Q5) New questions - LOTS of RCV failures (495) and send failures (156). What causes these? We defintely have firewalls in between and caught this issue last week, but is that what these types of errors are from or something else?

          It seems this MOVE server is performing far better than the first server I listed about. waitt ime is half 0.000012 sec vs 0.000030 sec. Process time is 0.125 vs. 0.148. All around I see better stats on this one if I'm reading correctly.