caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Eray Ozkural <examachine@gmail.com>
To: Michael Ekstrand <michael@elehack.net>
Cc: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] performance of ocamlgraph and ocaml batteries
Date: Mon, 13 Dec 2010 17:02:04 +0200	[thread overview]
Message-ID: <AANLkTi=eAYURHwSSt9=PadmLym7dWmnAGxsu_K2rR=5f@mail.gmail.com> (raw)
In-Reply-To: <4D0631FD.6000106@elehack.net>

[-- Attachment #1: Type: text/plain, Size: 987 bytes --]

On Mon, Dec 13, 2010 at 4:47 PM, Michael Ekstrand <michael@elehack.net>wrote:
>
> > 2. Generally, is the memory consumption of ocamlgraph is effective?
>
> In my experience, it is quite reasonable in its memory use (particularly
> compared with a Java library I tried).  The ultimate test, though, is
> your application.  Can you do the computations you need within the
> resources you have available?  I'm guessing it'll be pretty hard to beat
> ocamlgraph, though, except with a very tight array-based implementation
> with integer nodes.
>
>

Oww, is the imperative implementation using hash tables or maps then? You
can always implement an adjacency list structure with dynamically sized
arrays. That's what boost::graph does. Shouldn't be too hard to plug your
own in ocamlgraph if needed.

Cheers,


-- 
Eray Ozkural, PhD candidate.  Comp. Sci. Dept., Bilkent University, Ankara
http://groups.yahoo.com/group/ai-philosophy
http://myspace.com/arizanesil http://myspace.com/malfunct

[-- Attachment #2: Type: text/html, Size: 1523 bytes --]

  reply	other threads:[~2010-12-13 15:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-13  5:09 Kihong Heo
2010-12-13 14:47 ` [Caml-list] " Michael Ekstrand
2010-12-13 15:02   ` Eray Ozkural [this message]
2010-12-13 15:51     ` Julien Signoles
2010-12-14 11:02       ` Eray Ozkural

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='AANLkTi=eAYURHwSSt9=PadmLym7dWmnAGxsu_K2rR=5f@mail.gmail.com' \
    --to=examachine@gmail.com \
    --cc=caml-list@yquem.inria.fr \
    --cc=michael@elehack.net \
    /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).