[
https://issues.apache.org/jira/browse/GEODE-6005?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jacob S. Barrett updated GEODE-6005:
------------------------------------
Description:
There is a process global lock for protecting something called "big buffer" but
there is no big buffer. It looks like it may just restrict other threads from
creating big buffers while another thread has a big buffer. Let's investigate
what is really going on here and understand why and if we need to do this.
I think a better solution to resource management would be a bounded buffer pool
where DataOutput/Input would checkout buffers to some user configurable limit
before blocking.
was:There is a process global lock for protecting something called "big
buffer" but there is no big buffer. It looks like it may just restrict other
threads from creating big buffers while another thread has a big buffer. Let's
investigate what is really going on here and understand why and if we need to
do this.
> Investigate DataOutput's "big buffer"
> -------------------------------------
>
> Key: GEODE-6005
> URL: https://issues.apache.org/jira/browse/GEODE-6005
> Project: Geode
> Issue Type: Task
> Components: native client
> Reporter: Jacob S. Barrett
> Priority: Major
>
> There is a process global lock for protecting something called "big buffer"
> but there is no big buffer. It looks like it may just restrict other threads
> from creating big buffers while another thread has a big buffer. Let's
> investigate what is really going on here and understand why and if we need to
> do this.
>
> I think a better solution to resource management would be a bounded buffer
> pool where DataOutput/Input would checkout buffers to some user configurable
> limit before blocking.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
