From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Original-To: caml-list@sympa.inria.fr Delivered-To: caml-list@sympa.inria.fr Received: from mail2-relais-roc.national.inria.fr (mail2-relais-roc.national.inria.fr [192.134.164.83]) by sympa.inria.fr (Postfix) with ESMTPS id 262AF7F30A for ; Tue, 26 Feb 2013 05:30:04 +0100 (CET) Received-SPF: None (mail2-smtp-roc.national.inria.fr: no sender authenticity information available from domain of ygrekheretix@gmail.com) identity=pra; client-ip=209.85.220.44; receiver=mail2-smtp-roc.national.inria.fr; envelope-from="ygrekheretix@gmail.com"; x-sender="ygrekheretix@gmail.com"; x-conformance=sidf_compatible Received-SPF: Pass (mail2-smtp-roc.national.inria.fr: domain of ygrekheretix@gmail.com designates 209.85.220.44 as permitted sender) identity=mailfrom; client-ip=209.85.220.44; receiver=mail2-smtp-roc.national.inria.fr; envelope-from="ygrekheretix@gmail.com"; x-sender="ygrekheretix@gmail.com"; x-conformance=sidf_compatible; x-record-type="v=spf1" Received-SPF: None (mail2-smtp-roc.national.inria.fr: no sender authenticity information available from domain of postmaster@mail-pa0-f44.google.com) identity=helo; client-ip=209.85.220.44; receiver=mail2-smtp-roc.national.inria.fr; envelope-from="ygrekheretix@gmail.com"; x-sender="postmaster@mail-pa0-f44.google.com"; x-conformance=sidf_compatible X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AukBAEU5LFHRVdwsm2dsb2JhbABFwWGBAxYOAQEBAQEGCwsJFCeCHwEBBAE6BgEbHQEDAQsGBQsNHBIjEQEFARwGE4gAAQMJBQEMoWSMMoFxgQqESQoZJw1ZiHsBBQyPAgeDQAOIZ4VIhE2DQAGBHY1mP4Q3 X-IPAS-Result: AukBAEU5LFHRVdwsm2dsb2JhbABFwWGBAxYOAQEBAQEGCwsJFCeCHwEBBAE6BgEbHQEDAQsGBQsNHBIjEQEFARwGE4gAAQMJBQEMoWSMMoFxgQqESQoZJw1ZiHsBBQyPAgeDQAOIZ4VIhE2DQAGBHY1mP4Q3 X-IronPort-AV: E=Sophos;i="4.84,737,1355094000"; d="scan'208";a="4470046" Received: from mail-pa0-f44.google.com ([209.85.220.44]) by mail2-smtp-roc.national.inria.fr with ESMTP/TLS/RC4-SHA; 26 Feb 2013 05:30:03 +0100 Received: by mail-pa0-f44.google.com with SMTP id kp1so2186769pab.17 for ; Mon, 25 Feb 2013 20:30:01 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:date:from:to:cc:subject:message-id:in-reply-to :references:x-mailer:mime-version:content-type :content-transfer-encoding; bh=DXYLribJ/SbDw+O+Lfs18mBA5Z1HBW8JLARTwtjHu+Q=; b=WIqDJuQsYT5ojQ8uiOHzc9X2kX8C7mSLMfNSH9QnV1IDudS0ZjCES/t5gfPxMMkBqe pFZ37G5hbx0OOx3HtPOH4MEV7PVziHP+vMhUcvuldBU7sKRcFgp2KxGti0nzOYpz9t3X Ja1m2nDTTHGJOFqQ55feMBgyCeQuUtuiYFmuJg1KZNNizlWXtNsBah0qpvHEVR5fuBH0 t13/OZujZlQD7wR4Xi40W6RNLZ1FcIayRtYoWQgqHAfPLWSPto4DATi3kfUYYMYHkFNc IpY0Y4MYbASMW2cU8TQuqFT89xz4IN4Hh1QonuPIfG2pXngKcb/f87hOBJrZMobjcYKO EICA== X-Received: by 10.67.1.74 with SMTP id be10mr22399648pad.172.1361853001520; Mon, 25 Feb 2013 20:30:01 -0800 (PST) Received: from kiwi.local.tld ([180.129.86.20]) by mx.google.com with ESMTPS id tp2sm14997398pbc.12.2013.02.25.20.29.59 (version=TLSv1.2 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 25 Feb 2013 20:30:00 -0800 (PST) Date: Tue, 26 Feb 2013 12:29:57 +0800 From: ygrek To: Francois Berenger Cc: caml-list@inria.fr Message-Id: <20130226122957.935315debde1b1224e4dd35a@gmail.com> In-Reply-To: <512C2FFD.9070606@riken.jp> References: <512AC78E.7070908@riken.jp> <20130225183222.8f7eda023079e8ddf31e3f5f@gmail.com> <512C2FFD.9070606@riken.jp> X-Mailer: Sylpheed 3.2.0 (GTK+ 2.24.10; x86_64-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: [Caml-list] What is triggering a lot of GC work? On Tue, 26 Feb 2013 12:46:05 +0900 Francois Berenger wrote: > On 02/25/2013 07:32 PM, ygrek wrote: > > On Mon, 25 Feb 2013 08:02:54 +0000 > > Mark Shinwell wrote: > > > >> On 25 February 2013 02:08, Francois Berenger wrote: > >>> Is there a way to profile a program in order > >>> to know which places in the source code > >>> trigger a lot of garbage collection work? > >> > >> Well, as of last week, there is! > >> > >> I'm working on a compiler and runtime patch which allows the > >> identification, without excessive overhead, of every location (source > >> file name / line number) which causes a minor or major heap allocation > >> together with the number of words allocated at that point. > >> > >> There should be something available within the next couple of weeks. > >> It only works on native code compiled for x86-64 machines at present. > >> Currently it has only been tested on Linux---although I expect it to > >> work on other Unix-like platforms with little or no modification. > > > > Meanwhile you can use poor man's allocation profiler : > > - http://ygrek.org.ua/p/code/pmpa > > - https://sympa-roc.inria.fr/wws/arc/caml-list/2011-08/msg00050.html > > Did the changes reported on mldonkey to do less allocations had a > significant impact on performances? Unfortunately, there was no feedback from the users of embedded versions of mldonkey, who have constrained memory and cpu resources, but there were no performance problems reported since then either, so it is hard to tell. -- ygrek http://ygrek.org.ua