From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:55621) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1eBi59-0001xf-TS for qemu-devel@nongnu.org; Mon, 06 Nov 2017 09:08:56 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1eBi55-0007rt-TG for qemu-devel@nongnu.org; Mon, 06 Nov 2017 09:08:55 -0500 Received: from mx1.redhat.com ([209.132.183.28]:32834) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1eBi55-0007ra-Nc for qemu-devel@nongnu.org; Mon, 06 Nov 2017 09:08:51 -0500 References: <80415da5-4eef-bf85-b617-fadc3dae4475@redhat.com> <20171106115931.GB3898@lemon> From: Paolo Bonzini Message-ID: <78a404c5-fb2f-6fdf-c307-107ff1af4342@redhat.com> Date: Mon, 6 Nov 2017 15:08:45 +0100 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] qemu core file size List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Wanpeng Li Cc: Fam Zheng , Alexey Kardashevskiy , "qemu-devel@nongnu.org Developers" On 06/11/2017 13:18, Wanpeng Li wrote: > 2017-11-06 20:02 GMT+08:00 Paolo Bonzini : >> On 06/11/2017 12:59, Fam Zheng wrote: >>>>> Could you point out the patchset for the fix? >>>> Between 447b0d0b9ee8a0ac216c3186e0f3c427a1001f0c and >>>> 092aa2fc65b7a35121616aad8f39d47b8f921618. >>> Not sure how these relate to the core size, but I've tested upstream >>> (ec7a8bf0b8f7dc7288fe8745464ee8217528cc6c) and with dump-guest-core=off the core >>> file is 363M, still significantly larger than rss (~73M). >>> >>> What is bloating the core file? >> >> My guess would have been fragmented heap. The core file, unlike the >> RSS, includes all the mmaped memory (e.g. from shared libraries) that >> has never been used. >> >> For example, all the Ceph/Gluster/PulseAudio/SPICE/whatever libraries >> are included in the core file but likely are not in the RSS. > > Do you mean not use Memory API will avoid the fragmented heap? The high memory usage from the memory API causes excessive fragmentation. Alexey's work should help reducing memory usage and thus the fragmentation. Paolo