You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mina.apache.org by "Mark Webb (JIRA)" <ji...@apache.org> on 2008/08/04 03:47:44 UTC

[jira] Commented: (DIRMINA-519) BufferingFilter

    [ https://issues.apache.org/jira/browse/DIRMINA-519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12619401#action_12619401 ] 

Mark Webb commented on DIRMINA-519:
-----------------------------------

These are my results on an OS X machine running Java 1.6.0_05

CPU = 2.4GHz Core 2 Duo


Map type:           ConcurrentHashMap
Runtime:            60000
Number of threads:  3
Remove probability: 0.1
Ops per second:     17204.25

Map type:           HashMap
Runtime:            60000
Number of threads:  3
Remove probability: 0.1
Ops per second:     107432.13333333333

Map type:           LazyInitializedCacheMap
Runtime:            60000
Number of threads:  3
Remove probability: 0.1
Ops per second:     55034.433333333334

Hope this helps....


> BufferingFilter
> ---------------
>
>                 Key: DIRMINA-519
>                 URL: https://issues.apache.org/jira/browse/DIRMINA-519
>             Project: MINA
>          Issue Type: New Feature
>          Components: Filter
>            Reporter: Trustin Lee
>            Assignee: Edouard De Oliveira
>            Priority: Minor
>             Fix For: 2.0.0-M3
>
>         Attachments: test.rar
>
>
> As JDK provides BufferedOutputStream, we could provide BufferingFilteer which does the same thing, which buffers encoded data and flushes it out when the buffer becomes full or the flush operation is explicitly requested.  This kind of filter is sometimes useful when a session is generating very small messages too frequently and consequently generates unnecessary traffic overhead.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.