All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ming Zhang <blackmagic02881@gmail.com>
To: linux-btrace@vger.kernel.org
Subject: Re: memory used by btt
Date: Tue, 27 Mar 2007 01:20:25 +0000	[thread overview]
Message-ID: <1174958425.5930.12.camel@localhost.localdomain> (raw)
In-Reply-To: <1174922598.3667.27.camel@dhcp-119.ibrix.com>

On Mon, 2007-03-26 at 12:17 -0400, Alan D. Brunelle wrote:
> Ming Zhang wrote:
> > Hi 
> >
> > I am now using btt to analyze a 700MB trace data and it always run oom
> > in my 2GB ram laptop. it also eat 2GB swap as well. Any idea why btt
> > need so many memory?
> >   
> 
> Well, BTT builds trees based upon outstanding IO traces. That could 
> indicate that BTT is having a hard time dealing with your data - I find 
> that sometimes the kernel does weird things, causing strange IO trees 
> being built that BTT can't put back together. I've got some multi-GB 
> sized binary files that I've handled, let me see what the memory 
> footprint is for those...
> 
> 
> > ps, why we always need double in the code, can float fit the bill as
> > well?
> >   
> 
> Probably could, but I'm not too sure about some of the conversions done 
> with LBAs. I can look into that if need be.

i did a quick check, changing to float will not have much help on that
footprint. double is not used in some key data structures.

> 
> Alan
> 
> > Ming
> >
> >   
> 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-btrace" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html


      parent reply	other threads:[~2007-03-27  1:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-26 15:23 memory used by btt Ming Zhang
2007-03-26 16:17 ` Alan D. Brunelle
2007-03-27  1:20 ` Ming Zhang [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1174958425.5930.12.camel@localhost.localdomain \
    --to=blackmagic02881@gmail.com \
    --cc=linux-btrace@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.