ATS versions - 6.2.1 and 7.0.0 Cache disk - 18G ramdisk - /dev/ram0 System memory - 32G Traffic type - HLS Live
While testing live HLS traffic, I noticed that ATS 6.2.1. continued to use ramdisk until eventually traffic_server was restarted(via trafic_cop) as result of 'oom killer' Testing with ATS 7.0.0 I saw memory use remain stable once the ramdisk reached it's 'configured' capacity. I looked through the 7.0 changelog and didnt see anything obvious, so maybe someone is aware of an undocumented change which impacts ATS 'honoring' configured ramdisk boundaries. Understood ATS may not know the difference between /dev/sdX and /dev/ramX.. But just putting this out to the community just in case I am missing something. Jeremy
