search

mgchetla / jmesa

Automatically exported from code.google.com/p/jmesa
0 stars 0 forks source link

JMesa seems too slow with many records #291

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
I have a table with 900 records, but it loads too slow, either in their 
original state or to search, paging, exporting, etc. Is there any way to 
optimize the amount of information shown by JMesa?

Original issue reported on code.google.com by andyned...@gmail.com on 11 Oct 2010 at 4:11

GoogleCodeExporter commented 8 years ago 
JMesa uses the same amount of resources regardless of the amount of rows that 
you have. It is the memory and time spent in creating the rows (beans) that are 
slowing you down. What you can do is use the Limit to efficiently just return 
one row at a time. However, when you just return one page of information you 
have to handle the sorting and filtering yourself.

http://code.google.com/p/jmesa/wiki/LimitTutorialV3

I am surprised that 900 rows is slowing you down. Usually it takes a few 
thousand before you will start noticing...but it totally depends on your 
environment.

Original comment by jeff.johnston.mn@gmail.com on 18 Oct 2010 at 9:22

GoogleCodeExporter commented 8 years ago 
You're right. I use JMesa with OpenCms, and access to get the records I list is 
no database, but XML file structures. Thus, if I have 900 records 900 times I 
have to access to XML files for individual information, go add each record to a 
variable of type List, and at the end Ipass that variable to list it with JMesa.

Maybe 0.15 mil to get the information from XML is not very slow, but with 900 
records is increased time and it shows.

Original comment by andyned...@gmail.com on 19 Oct 2010 at 6:41

GoogleCodeExporter commented 8 years ago

Original comment by jeff.johnston.mn@gmail.com on 9 Mar 2011 at 7:34