> > Each thread is killed after work is done
> How do you "kill" the threads? I hope this is just a figure of
> speech for "I do an orderly shutdown of each thread after work is done."
Well, that was consequence of my bad English :-) Threads finish their
work and exit. I also made a simple wrappe
John Lepikhin schrieb:
> Each thread is killed after work is done
How do you "kill" the threads? I hope this is just a figure of
speech for "I do an orderly shutdown of each thread after work is done."
- Florian.
___
Caml-list mailing list. Subscriptio
> > Please, give me some start point to find the roots of the problem.
> I assume you're running on Linux.
I've got this issue on FreeBSD box. On Linux test box process grows only
up to 2MB (but there is no production data and clients). Here is partial
pmap output:
Address Kbytes
> Starting point should be to call this periodically:
>
> Gc.compact ();
> let stat = Gc.stat () in
> let live_words = stat.Gc.live_words in
> eprintf "live words %d\n%!" live_words;
>
> which will tell you how many words (ie 4 or 8 byte chunks) are
> reachable according t
On Mon, Jan 12, 2009 at 03:41:46PM +0800, John Lepikhin wrote:
> Please, give me some start point to find the roots of the problem.
Starting point should be to call this periodically:
Gc.compact ();
let stat = Gc.stat () in
let live_words = stat.Gc.live_words in
eprintf "l
Hello,
I have developed an application and have issue with memory usage.
Application was designed for work as server, 24x7. After several hours
of work, RSS memory grows up to 40-50MB. Each thread must not use more
than 100-200KB of memory (maximum 20 threads are run at the same time).
GC debug in
I agree. I should use Int64 instead of just int, but I still think
that the application (Random.int max_int) should not be exception
prone. Since max_int is architecture dependent, then so should be
Random.int no?
But you point is well taken. Thanks again
J
On Wed, Jul 16, 2008 at 2:44 PM, Andre
On Jul 16, 2008, at 2:07 PM, Jean Krivine wrote:
Good news, I just tested the patch and it works great with my
application!
I just had to modify the module random since a call to (Random.int
max_int) may raise and exception (it is made for 32 bits integers).
So I guess that modification shou
Good news, I just tested the patch and it works great with my application!
I just had to modify the module random since a call to (Random.int
max_int) may raise and exception (it is made for 32 bits integers).
So I guess that modification should be included in the patch.
Thanks a lot Andres.
Jean
Great thanks!
J
On Wed, Jul 16, 2008 at 10:16 AM, Andres Varon <[EMAIL PROTECTED]> wrote:
>
> On Jul 15, 2008, at 3:38 PM, Jean Krivine wrote:
>
>> I'd be glad to try the patch if you could post it somewhere!
>
> I have posted it in:
>
> http://research.amnh.org/~avaron/ocaml/
>
> best,
>
> Andre
On Jul 15, 2008, at 3:38 PM, Jean Krivine wrote:
I'd be glad to try the patch if you could post it somewhere!
I have posted it in:
http://research.amnh.org/~avaron/ocaml/
best,
Andres
J
On Tue, Jul 15, 2008 at 3:31 PM, Andres Varon <[EMAIL PROTECTED]>
wrote:
Hello Jean,
There is no
I'd be glad to try the patch if you could post it somewhere!
J
On Tue, Jul 15, 2008 at 3:31 PM, Andres Varon <[EMAIL PROTECTED]> wrote:
> Hello Jean,
>
> There is no 64-bit native OCaml compiler for Mac OS X intel. I have a patch
> that works in Leopard, but did not compile opt.opt in Tiger, mea
Hello Jean,
There is no 64-bit native OCaml compiler for Mac OS X intel. I have a
patch that works in Leopard, but did not compile opt.opt in Tiger,
meaning that something is not OK, so I did not offer it to the
community. The bootstrap went fine, findlib and godi compiled OK too.
I can
Dear all
I downloaded the last version of ocaml (3.10.2) but I must confess I
don't know what option I should pass to the compiler to make a binary
that uses 64 bits.
I tried naively ocamlopt -ccopt -arch -ccopt x86_64 but that doesn't
work. Any idea?
On Fri, Jul 11, 2008 at 6:01 PM, Richard Jo
On Fri, Jul 11, 2008 at 03:49:26PM -0400, Jean Krivine wrote:
> I am trying to run a stochastic simulator (written in ocaml) on a huge
> data set and I have the following error message:
I can confirm that OCaml works fine with huge datasets, on 64 bit
platforms anyway.
> sim(9595) malloc: *** mma
It is hard to tell without any more informations but sometimes the
garbage collector needs some gentle proding:
OCaml handles it's own memory but can be a bad citizen when it comes
to making room for others. Unfortunately ocaml also has a bit of a
double personality: it doesn't know much about res
Dear list members,
I am trying to run a stochastic simulator (written in ocaml) on a huge
data set and I have the following error message:
sim(9595) malloc: *** mmap(size=1048576) failed (error code=12)
*** error: can't allocate region
*** set a breakpoint in malloc_error_break to debug
Fatal err
17 matches
Mail list logo
