Significantly different CPU usage on HLS load testing tools

Running Wowza 4.7.2 and am trying to load test our environment to move over to HLS from RTMP. I’m testing with both the Wowza load test tool and the Blazemeter HLS plugin for jMeter. I’m having both tools test using the same URL http://node1.example.com/live/definst/myStream/playlist.m3u8. No transcoding or transrating is being done on the wowza server side. The test is being run with 300 users.

When running the test, the CPU usage on the wowza server is significantly different depending on which tool is being used. With the wowza load testing tool I’m getting about 20% CPU usage. However, with the jMeter tool I’m getting about 80% CPU utilization. See screenshot below. I’m not seeing any noticeable differences in the wowza access logs on how connections are being created or anything like that. Any suggestions on how to determine what could be different?

Here are screenshots of the jMeter configs.