You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@uima.apache.org by "Richard Eckart de Castilho (JIRA)" <de...@uima.apache.org> on 2016/09/09 17:48:23 UTC

[jira] [Updated] (UIMA-1090) Add tooling to measure things for tuning space/time

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

Richard Eckart de Castilho updated UIMA-1090:
---------------------------------------------
    Labels: Stale  (was: )

This issue is marked as "stale" due to inactivity for 5 years or longer. If no further activity is detected on this issue, it is scheduled be closed as 'unresolved' in 3 months time from now (Dec 2016).

> Add tooling to measure things for tuning space/time
> ---------------------------------------------------
>
>                 Key: UIMA-1090
>                 URL: https://issues.apache.org/jira/browse/UIMA-1090
>             Project: UIMA
>          Issue Type: Improvement
>          Components: Core Java Framework
>    Affects Versions: 2.2.2, 2.3
>            Reporter: Marshall Schor
>            Priority: Minor
>              Labels: Stale
>
> Some fairly simple tooling could help users discover easy things to do to tune their UIMA application.  One such tool might measure the % of space in the CAS used by unused features.  This might occur when using a general component that could set many feature fields, but intentionally running it in a mode where many of the fields are unused.  In this case, changing the type definition to exclude those fields would save space in the CAS, which could be significant in those cases where a lot of instances of those types are created (e.g., tokens).
> Such a tool could be packaged as a JMX measurement, or as a special annotator, or as some new part of the framework.



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