directmemory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christoph Engelbert (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DIRECTMEMORY-66) don't expose parameters of other libraries / concurrencylevel
Date Thu, 01 Nov 2012 12:27:12 GMT

    [ https://issues.apache.org/jira/browse/DIRECTMEMORY-66?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13488639#comment-13488639
] 

Christoph Engelbert commented on DIRECTMEMORY-66:
-------------------------------------------------

The concurrencylevel could be used for other tasks as well, for example like preallocation
multiple partitions of big buffers (Unsafe memory access) and sharing them.
                
> don't expose parameters of other libraries / concurrencylevel
> -------------------------------------------------------------
>
>                 Key: DIRECTMEMORY-66
>                 URL: https://issues.apache.org/jira/browse/DIRECTMEMORY-66
>             Project: Apache DirectMemory
>          Issue Type: Improvement
>            Reporter: Daniel Manzke
>
> You should not expose parameters of other libraries like the concurrencylevel. Everybody
who wants to use DM should be able to configure the system without having to look into the
code.
> I know where the parameter comes from. (MapMaker / guava) But try to think like somebody
who has checked out DM from maven and tries to start with it. (ok there is a default)
> Should be removed or encapsulated. (Enumeration?)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message