Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings

DirectBufferProxy uses unnecessary concurrent queue for object pool #200

Copy link
Copy link
@danielcranford

Description

@danielcranford
Issue body actions

Unnecessary since the queue object is thread local. poll() and offer() are likely more expensive than a simple ArrayDeque which is used in the ByteBufferProxy object pool implementation. Additionally, concurrent queue is fixed size meaning the offer() in DirectBufferProxy.deallocate() can fail abandoning the DirectBuffer to be garbage collected (though perhaps this is desired?) unlike the ArrayDeque used in ByteBufferProxy which resizes it's capacity when offer() is called while full.

Reactions are currently unavailable

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      Morty Proxy This is a proxified and sanitized view of the page, visit original site.