Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

resource consumption when compiling arrays #8498

Closed
vicuna opened this issue Mar 3, 2004 · 2 comments
Closed

resource consumption when compiling arrays #8498

vicuna opened this issue Mar 3, 2004 · 2 comments

Comments

@vicuna
Copy link

vicuna commented Mar 3, 2004

Original bug ID: 2306
Reporter: administrator
Status: closed (set by @mshinwell on 2016-12-07T16:25:59Z)
Resolution: not a bug
Priority: normal
Severity: feature
Category: ~DO NOT USE (was: OCaml general)

Bug description

Full_Name: Achim Blumensath
Version: 3.07
OS: Linux
Submission from: igloo.labri.fr (147.210.9.44)

I've noticed that ocamlopt uses a lot of time, memory, and
stack space when compiling arrays. It seems that some of the
functions used to compile arrays are not tail-recursive.

I have one file solely consisting of about 2000 arrays of
size 256 containing strings, integers, or pointers to some
of the other arrays. To compile this file, ocamlopt needs
several minutes and between 16k and 32k of stack space. With
256 MB of memory it even starts swapping at the end of the
compilation. I can provide the source code if needed.

@vicuna
Copy link
Author

vicuna commented Apr 1, 2004

Comment author: administrator

Should check where the time is spent and whether there is something obviously
fixable. But input file is huge and it's not surprising ocamlopt takes time on
it.

@vicuna
Copy link
Author

vicuna commented Dec 7, 2016

Comment author: @mshinwell

Given that the input file was not provided and the typical resource limits of today's systems I'm not sure there is anything to do here. More specific reports are welcome when compilation speed problems are found.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant