Hi, For some reason I thought I had this nailed but ... obviously not.
I have a 16GB physical machine with 64GB swap on "spinning" hard drives. I build an LX zone with a physical limit of 4GB and 8GB swap. If I log into my zone and allocate "too much" memory ( python3 -c "bytearray(8*1024*1024*1024)" ) then the swap starts thrashing and vfsstat reports long write times for the zone (of the order 2000us). After a couple of minutes the process closes due to signal 7. However, if another zone does the same thing then the global zone seems to bear the brunt of it. Write latencies go up to, in some cases, an entire second ... vmstat reports all the threads waiting, the free space scanner going mad, and eventually the box locks up solid. This happens regardless of whether or not rcap is running. I'm pretty sure this is not the ideal result - can anyone shed light on what's going on and how I might prevent it? Cheers, Dave ------------------------------------------- smartos-discuss Archives: https://www.listbox.com/member/archive/184463/=now RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00 Modify Your Subscription: https://www.listbox.com/member/?member_id=25769125&id_secret=25769125-7688e9fb Powered by Listbox: http://www.listbox.com
