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

Already on GitHub? Sign in to your account

Allow user to specify maximum size of GC allocation on command line #263

Closed
coke opened this Issue Dec 19, 2008 · 5 comments

Comments

Projects
None yet
4 participants
Contributor

coke commented Dec 19, 2008

We should have a command line option for parrot that allows us to specify the maximum amount of memory the GC is allowed to allocate

Originally http://trac.parrot.org/parrot/ticket/67

Owner

leto commented May 20, 2011

Isn't this already implemented?

Can this feature even *be* implemented in a way that makes sense across all the GC's we support?

Contributor

coke commented May 20, 2011

Replying to dukeleto:

Isn't this already implemented?

No.

Can this feature even *be* implemented in a way that makes sense across all the GC's we support?

I don't see why not; If it only makes sense for some GCs, I think we still need to implement it there; kind of a built in ulimit.

Contributor

Whiteknight commented May 9, 2012

The mem_limit branch implements the machinery necessary to take a memory limit from the commandline and pass it down into the gc_private structure for use by the GC. We don't currently have any way to use that flag (especially since so many places in our code use malloc/realloc/free directly) but the information can be made available if the memory subsystem ever chose to use it.

I don't think we should close this ticket yet, but I do want to say that we have part of the work done and the rest of it may be a herculean task for relatively little payoff.

Contributor

coke commented May 9, 2012

FYI, this feature request is inspired by java. We use this feature daily in our work environment (in java) to insure that multiple copies of the JVM do not starve resources on any given box.

Without this feature or something like it, I personally would have a hard (HARDER) sell using parrot on a work project.

Member

rurban commented Dec 29, 2014

We implemented this in the rather conventional way, supporting system-resource limits, i.e. the ulimit shell builtin.

See #935.

@rurban rurban closed this Dec 29, 2014

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