[jboss-jira] [JBoss JIRA] (WFLY-2838) Revisit default mod_cluster metric for WildFly 8

[Radoslav Husar (JIRA)]

    [ https://issues.jboss.org/browse/WFLY-2838?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12940525#comment-12940525 ] 

Radoslav Husar commented on WFLY-2838:
--------------------------------------

JFC would prefer autogenerating capacity of the busyness metric (e.g. in JBW it is 128 requests per sec per CPU) [or session.]
                
> Revisit default mod_cluster metric for WildFly 8
> ------------------------------------------------
>
>                 Key: WFLY-2838
>                 URL: https://issues.jboss.org/browse/WFLY-2838
>             Project: WildFly
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Clustering
>    Affects Versions: 8.0.0.CR1
>            Reporter: Radoslav Husar
>            Assignee: Radoslav Husar
>            Priority: Blocker
>             Fix For: 8.0.0.Final
>
>
> Since the threading aspects of Undertow in WildFly are completely different from JBoss Web's in the previous versions of AS, we should reconsider the default metric for WildFly.
> Currently, busyness requires explicit capacity to be useful which would require further tweaking by users.
> Metric "cpu" is also a good candidate since it doesn't need explicit capacity.. 

--
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