JPA Container performance

Vaadin 6 / 7 / 8 Framework Data Binding
1

Hi,

I am migrating a “traditional” web based two-tier system to a “state-of-the-art” multi-tier solution. I have migrated the old datamodel to a complete new (JPA-2 annotated) domainmodel and at the moment I am migrating the DAO’s and the most simple 3 web page application.

One of the overview pages contains a tabpanel with 3 tabs, each with a 25 item table. Each table shows 5/6 columns. When I change data, data is removed from one table and added to another. Nothing complex.
I use a JPAContainer for each Table. Every container has a simple two attribute [NOT-]
NULL check filter. That’s all. There is an external process which adds items, so the containers are refreshed whenever status changes, or an item is added.

When I switched-on the sql-logging I found an impressive amount of executing queries. A COUNT, PAGING, ID-s and content retrieval. I tried to solve this by changing the provider (Caching etc., Read-Only), but whatever I do I can see that the number of queries is still too high. This is still in a test-phase, so you can imagine that with a serious amount of users this will become a show-stopper.

I’ve already seen some remarks that I shouldn’t use the JPAContainer because of of its bad performance, but it is isn’t clear if this is solved or will be solved in the near future.

I would be helped a lot if somebody could inform me about the status of the (certified!) JPAContainer , if the performance is still a serious issue and will be handled by on the short term.

Thanks in advance!

2

Not sure if they (vaadin-devs) are currently working on the performance issues of JPAContainer.

If you work with large datasets , I would suggest you use the
LazyQueryContainer
, I moved two projects to it without much hassle.

3

Hi Petrus,

Thanks for your reply. In other subprojects I will certainly give it a try. Because it’s just a small dataset I am using a simple BeanContainer now, backed by a session bean (a repository implementation, not the ejb solution though) . Works like a charm!

To be honest I am a bit surprised/disappointed : I can imagine that if Vaadin calls something a “certified” plugin it has to meet some (thoroughly tested) quality standards. But unfortunately i’ve found this remark: “…Add-on is tested for 1-2 hours to see if it works in practice…” Maybe this works for (simple) UI-components, but this is certainly not enough for infrastructure components such as JPAContainer. Hopefully I am not going to encounter more of these kind of nice “surprises” in the near future.

Let’s wait and see if somebody of the vaadin-devs can shed some light on this issue.

Leo