caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: 沈胜宇 <syshen@nudt.edu.cn>
To: "David House" <dhouse@janestreet.com>
Cc: "Malcolm Matalka" <mmatalka@gmail.com>, caml-list <caml-list@inria.fr>
Subject: Re: Re: [Caml-list] [OCAML]:: the cost of List.length
Date: Mon, 15 Apr 2013 19:05:19 +0800 (GMT+08:00)	[thread overview]
Message-ID: <2b3ad45a.48f7.13e0d5ed8c7.Coremail.syshen@nudt.edu.cn> (raw)
In-Reply-To: <CAK=fH+iayL1PmbZnu4MS4t68cgm0G-7k0i4QVR410N1dtBYNqg@mail.gmail.com>

Dear all:

I have found that the slow down of my program is not caused by the List.length directly, instead, the list length operation cause some different change in my control flow, that is the direct cause of my slow down.

but still thank you for your help.

Shen


> -----原始邮件-----
> 发件人: "David House" <dhouse@janestreet.com>
> 发送时间: 2013-04-15 14:29:21 (星期一)
> 收件人: "Malcolm Matalka" <mmatalka@gmail.com>
> 抄送: "沈胜宇" <syshen@nudt.edu.cn>, caml-list <caml-list@inria.fr>
> 主题: Re: [Caml-list] [OCAML]:: the cost of List.length
> 
> Lists are naive linked lists, i.e. either the empty list or a pair of
> an element and a list. Finding the length means walking to the end of
> the list.
> 
> There is probably a better data structure than lists for your
> purposes. What operations do you need, and which ones need to be fast?
> 
> On 14 April 2013 14:32, Malcolm Matalka <mmatalka@gmail.com> wrote:
> > O(n)
> >
> > Den 14 apr 2013 15:27 skrev "沈胜宇" <syshen@nudt.edu.cn>:
> >
> >> Dear all:
> >>
> >> I have a program that run very fast.
> >>
> >> Recently, I add a call to List.length to this old program's inner loop,
> >> which make it significantly slower.
> >>
> >> So what is the cost of List.length, is it liner to the size of the list?
> >> or is a const?
> >>
> >> Shen


      reply	other threads:[~2013-04-15 11:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-14 13:23 沈胜宇
2013-04-14 13:32 ` Malcolm Matalka
2013-04-15  6:29   ` David House
2013-04-15 11:05     ` 沈胜宇 [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=2b3ad45a.48f7.13e0d5ed8c7.Coremail.syshen@nudt.edu.cn \
    --to=syshen@nudt.edu.cn \
    --cc=caml-list@inria.fr \
    --cc=dhouse@janestreet.com \
    --cc=mmatalka@gmail.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).