[
https://issues.apache.org/jira/browse/RAVE-838?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13487923#comment-13487923
]
Chris Geer commented on RAVE-838:
---------------------------------
Ate, I agree, the merge is causing the issues, just curious why it's so
dramatic on your box. One side effect of the split is that we have to retrieve
objects (Widgets, Users...) in more places now. My original intent was to do
caching along with the model split but since I wasn't seeing a dramatic
performance problem I wasn't as worried about it and decided to push for the
merge sooner. I guess that's the downside of having a relatively fast dev box.
There is no reason why we should be reading the same object from the DB
multiple times in short spans, there needs to be caching of some sort. Matt is
working on reducing the number of calls required to get a Widget which will
help but we still need to think about the caching. I understand JPA has
caching, but I really think putting caching at the Service layer might be the
best option since it would work regardless of the backend. Maybe use ehCache
like Shindig does as a default?
On a side note, using Rave against MySQL, I'm seeing the same performance now
as before the merge. I'm assuming MySQL is doing some level of caching of data
somewhere that H2 doesn't do.
> Performance problems after model-split merge
> --------------------------------------------
>
> Key: RAVE-838
> URL: https://issues.apache.org/jira/browse/RAVE-838
> Project: Rave
> Issue Type: Bug
> Affects Versions: 0.17
> Reporter: Chris Geer
> Assignee: Chris Geer
> Fix For: 0.17
>
>
> - WidgetServer/Repository.get is being called much more frequently with the
> RegionWidget/Widget split.
--
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
