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.

Sign up for GitHub

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

Jump to bottom

Need to bound the memory use of Jsonnet evaluation #6

Closed
sparkprime opened this issue Aug 10, 2014 · 1 comment
Closed

Need to bound the memory use of Jsonnet evaluation #6

sparkprime opened this issue Aug 10, 2014 · 1 comment
Labels
enhancement

Comments

@sparkprime
Copy link
Contributor

The interpreter currently knows how many objects are live, but not how large they are. If it had this extra information, it would be possible to place a bound on the amount of memory that can be used during execution. This makes it safer to run Jsonnet in a server environment.
@sparkprime sparkprime mentioned this issue Aug 16, 2016
Closed
@sparkprime
Copy link
Contributor Author

The most reliable way to do this is, e.g. when evaluating Jsonnet server side, is to fork a new process to run Jsonnet (e.g. just run the standard commandline binary) and then ulimit that process.

This was referenced Nov 20, 2023
Open
Open
sbarzowski pushed a commit to sbarzowski/jsonnet that referenced this issue Jun 10, 2024
@jbeda
Merge pull request google#6 from jbeda/fix-lint
3b5fc97 
Fix lint issues and add package comment
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@sparkprime