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

AKI-358: synchronize on account unlocking & locking #983

Merged
merged 1 commit into from
Sep 25, 2019
Merged

Conversation

aionick
Copy link
Contributor

@aionick aionick commented Sep 11, 2019

  • This is to fix an OutOfMemory issue that occurs when multiple rpc threads
    are attempting to unlock (or lock) accounts simultaneously. This is a very
    memory-intensive call, requiring 200-230MB of space for each call. The
    synchronization here prevents multiple threads from allocating this space
    concurrently and therefore allows for it to be gc'ed, keeping the memory
    usage low in this case.

- This is to fix an OutOfMemory issue that occurs when multiple rpc threads
  are attempting to unlock (or lock) accounts simultaneously. This is a very
  memory-intensive call, requiring 200-230MB of space for each call. The
  synchronization here prevents multiple threads from allocating this space
  concurrently and therefore allows for it to be gc'ed, keeping the memory
  usage low in this case.
@aionick aionick merged commit 6f91872 into master Sep 25, 2019
@aionick aionick deleted the nick-358 branch September 25, 2019 14:36
@AionJayT AionJayT added this to the 0.4.2 milestone Oct 7, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants