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

Memory locking for Windows [moved] #923

Closed
lvca opened this issue Dec 10, 2012 · 0 comments
Closed

Memory locking for Windows [moved] #923

lvca opened this issue Dec 10, 2012 · 0 comments

Comments

@lvca
Copy link
Member

lvca commented Dec 10, 2012

This is Issue 923 moved from a Google Code project.
Added by 2012-07-01T19:17:50.000Z by lomakin....@gmail.com.
Please review that bug for more context and additional comments, but update this bug.

Original labels: Type-Enhancement, Priority-Medium, Release, uateam

Original description

OrientDB release? 
r5977

Currently to avoid possible memory swapping issues we impelmented mlockall call on POSIX systems like Linux etc.  But we do not have similar functionality for Windows family. it will be nice to have similar one.
@lvca lvca closed this as completed Oct 3, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

1 participant