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

Require-lock granularity is far too big #71

Open
GoogleCodeExporter opened this issue Aug 23, 2015 · 0 comments
Open

Require-lock granularity is far too big #71

GoogleCodeExporter opened this issue Aug 23, 2015 · 0 comments
Labels
auto-migrated Priority-Medium Type-Defect

Comments

@GoogleCodeExporter
Copy link 

The require lock (basically a monitor) is currently helped per-runtime.  It
should be safe to hold per-realm (analysis needed).  Holding per-realm will
lower lock collisions on heaviliy multi-threaded applications, where each
thread is in a separate realm (i.e. worker thread model).

Original issue reported on code.google.com by wes.garl...@gmail.com on 17 May 2010 at 10:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
auto-migrated Priority-Medium Type-Defect
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@GoogleCodeExporter