10. When use HttpSession, the position that needs current office only as far as possible is saved among them, other content does not protect existence HttpSession in.
Enable conversational endurance.
It is very useful that HttpSessions uses order state information to memory. Its API is used easily and understand. Regretful is, development staff often forgot the purpose of HttpSession----With the user condition that will keep temporary. It is not aleatoric data cache. The conversation that we had seen too much system is every user put much data (achieve million byte) . Good, if have the user of 1000 entry systems at the same time, every user has the conversational data of 1MB, need 1G so or more memory are used at these conversation. Want to make these HTTP conversational data a few lesserer, otherwise, your property that uses a program will drop. One compares the conversational data that appropriate data bulk should be every user to be between 2K-4K about, this is not the regulation of a rigid, 8K still does not have a problem, but the speed when apparent meeting compares 2K wants slow. Must notice, do not make HttpSession turns data into the place of accumulation.
A common problem is use HttpSession cache a few information that establish very easily again, if be necessary. Because conversation is of endurance, undertake needless alignment is changed and keeping data is a kind of very extravagant decision. Contrarily, the haing rare watch in should using memory comes cache data, and a key word that has quotative to this data is saved in conversation. Such, if cannot log onto another applied servers successfully, can found data afresh.
When refer conversation endurance, do not forget summary enables this function. If you did not enable conversational endurance, or the server stopped because of some kind of reason (server breakdown or normal maintenance) , all the conversation of this current user that uses a service will be lost. This is an issue that makes a person very grouchy. The user must login afresh, and do a few businesses that they once had done afresh. Contrarily, if enabled conversational endurance, webSphere will be automatic the user (and their conversation) move to go up to another application server. The user does not know to be able to have the happening of this kind of thing even. The Bug that because the person makes be borne hard in code of consist in this locality,we once had seen system of a few products (the code that is not IBM! ) and the circumstance that breaks down suddenly, below this kind of circumstance, afore-mentioned functions still can move good.
11. In WebSphere, use dynamic cache, use mechanism of WebSphere Servlet cache.
Through using these functions, systematic performance can get very big rise, and expense is very small. And do not affect process designing model.
Passing cache to raise high-powered profit is well-known issue. Regretful is, current J2EE standard did not include a kind of mechanism that is used at Servlet/JSP cache. However, webSphere provided the support to page and bitty cache, through its dynamic cache function realizes this kind of support, and do not need correspondence make any changes with the program. The strategy of its cache is statement sex, and its are configured is to pass XML to configure a descriptor to come true. Accordingly, your applied process won't be affected, maintain as normative as J2EE compatibility and transplanting sex, property obtains in the cache mechanism that still reachs JSP from the Servlet of WebSphere at the same time optimize.
Previous 1 2 3 4 56 7 Next