java - Memory usage concern for using display:table jstl tag -


I use & lt; Display: table & gt; is written by my jsp & lt; Display: Table & gt; To pass an argument as an argument, there is a need for a live list. Currently, a controller will create a list, then JSP will display it.

My concern is that what will happen if 1000 users search at a time. This means that all results will need to be loaded for memory because & lt; Display: table & gt; To display different javabean lists running out of memory, the system will probably crash, is there a good strategy to stop the system running out of memory? Is there any way to limit the number of users to load the application? Does this mean that & lt; Display: table & gt; Is a bad programming practice because all records should be loaded into memory at a time? thank you in advanced.

This is a very legitimate concern. You should not assign unnecessary memory. DisplaysAlthough unfortunately does not support the PageGen at the database level. Everything should be loaded in Java memory first. The most memory-efficient approach is to clearly store data in only memory that is seeing a new HTTP request on the endusers server and to fix those new lines with DB on every button click Fire is on. .

No other JSP-based pagina tag that comes into mind. If you were using JSF, then I would have been recommended for this. You still have to type the code that is getting specific lines from the DB. But when you are using hibernate and / or jpa it is not difficult.

In "plain vanilla" JSP / JSTL you have to do a bit more work. In fact, you will have to provide a bunch of buttons which will modify the value of firstrow and DB Apply the action to obtain the data. I have answered this before.


Comments

Popular posts from this blog

c# - sqlDecimal to decimal clr stored procedure Unable to cast object of type 'System.Data.SqlTypes.SqlDecimal' to type 'System.IConvertible' -

Calling GetGUIThreadInfo from Outlook VBA -

Obfuscating Python code? -