You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, I was testing performances of Filtering Table (filteringtable-0.9.15.v7) in combination with the Vaadin JPA Container.
I know JPA Container is not a good choice, but this test helped me to find a possible improvement in the add-on's code.
In CustomTable.java method parseItemIdToCells at line 2276, there is a loop on columns which calls getContainerProperty a lot of times:
for (int j = 0; j < cols; j++) {
...
p = getContainerProperty(id, colids[j]);
...
This performs very badly with JPA Container, even if the Entity cached provider is employed.
Instead, if the enity item is gotten before the loop such as in the following example, then the performances are up to 300% better in my test:
Item item=getItem(id);
for (int j = 0; j < cols; j++) {
...
// p = getContainerProperty(id, colids[j]);
p = item.getItemProperty(colids[j]);
...
The text was updated successfully, but these errors were encountered:
andrealuciano71
changed the title
Improve performances in
Improve performances while getting Item properties in CustomTable.parseItemIdToCells
Apr 18, 2016
Hi, I was testing performances of Filtering Table (filteringtable-0.9.15.v7) in combination with the Vaadin JPA Container.
I know JPA Container is not a good choice, but this test helped me to find a possible improvement in the add-on's code.
In CustomTable.java method parseItemIdToCells at line 2276, there is a loop on columns which calls getContainerProperty a lot of times:
This performs very badly with JPA Container, even if the Entity cached provider is employed.
Instead, if the enity item is gotten before the loop such as in the following example, then the performances are up to 300% better in my test:
Regards,
Source.zip
Andrea
The text was updated successfully, but these errors were encountered: