[jira] Commented: (TOMAHAWK-843) myfaces not releasing memory gracefully?

["jens ludwig (JIRA)" <de...@myfaces.apache.org>]

    [ https://issues.apache.org/jira/browse/TOMAHAWK-843?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12466480 ] 

jens ludwig commented on TOMAHAWK-843:
--------------------------------------

Hello,

we are using Myfaces w/ Tomahawk, same versions, at Deutsche Bank for an intranet application to render large tables 
and are observing simillar memory issues during high workload.

Those HTML-Tables may grow up to 500 rows w/ about 20 cols.

We are still examing this issues and are trying to optimize our code but we would highly appreciate this issue to be observed.

With kind regards
Jens Ludwig


> myfaces not releasing memory gracefully?
> ----------------------------------------
>
>                 Key: TOMAHAWK-843
>                 URL: https://issues.apache.org/jira/browse/TOMAHAWK-843
>             Project: MyFaces Tomahawk
>          Issue Type: Bug
>    Affects Versions: 1.1.3
>         Environment: tomcat 5.5.12
>            Reporter: Dez
>
>  Hi,
>      I've been using Myfaces implementation of JSF for couple of months and just noticed that memory usage is pretty high - > many times I got out of memory error. It works fine for simple pages, but when the page is large and complex, it doesn't seem to release the memory used by component states.
> Here is the scenario:
>   I'm using t:datatable for rendering employees info. Each row corresponds to  a employee object, the row has 10 columns.
>  It works fine in terms of memory footprint and CPU, when the dataset the table renders is small, but when the size of the datasets is large(talking 
> about 500 or more),  I get Out of memory error even though the Managed Bean  is request-scoped.  No pagination being employed(that's the last resort). So when the number of user increases,  this leads to a serious issues of server crash, hang etc.
>    On profiling using yourtoolkit, I found that faces context never releases  the memory used by UI Components and the behaviour is erratic. The GC kicks 
> in after certain stage which is not very useful. Even for a table of small  data rows(20-30), it doesn't seem to release the memory, in fact it accumulates the memory.
>  So even the pagination doesn't seem to solve the out- of- memory issue as  the web site will be used by  large number of users. FYI, I'm using the
>  client STATE_SAVING_METHOD.
>  <context-param>
>          <param-name>javax.faces.STATE_SAVING_METHOD</param-name> 
>          <param-value>client</param-value>
>  </context-param>
>  Has anyone faced similar issues? Is this a bug or known issues of myfaces?
> No one seem to have resolved this issues, I did see similar issues being posted in different forums.
>  Would appreciate your help in this regard.
>  thanks
>  Dezmax

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira