[jira] [Updated] (EDGENT-194) Console: the "no metric" stream width scaling needs tweaking

["Susan L. Cline (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/EDGENT-194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Susan L. Cline updated EDGENT-194:
----------------------------------
    Component/s: Console

> Console: the "no metric" stream width scaling needs tweaking
> ------------------------------------------------------------
>
>                 Key: EDGENT-194
>                 URL: https://issues.apache.org/jira/browse/EDGENT-194
>             Project: Edgent
>          Issue Type: Bug
>          Components: Console
>            Reporter: Dale LaBossiere
>            Priority: Minor
>              Labels: newbie
>
> The scaling for a stream lacking metrics needs tweaking (e.g., the stream between the filter and peek: `... -> filter -> peek`  ; no sink).  
> The width of such a stream can end up being much larger than streams that have a larger actual flow.  A good heuristic for this case is:  #output tuples == #input tuples.
> This can easily be demonstrated by the SensorAnalyticsApplication sample, where there are widely disparate tuple flow rates -- e.g., 1k/sec and 1/sec.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)