- Fundamentals, topology and characteristics typical of environments with high availability and scalability; concepts of clusters (load balancing, fail-over and replication of state) and techniques for tuning and troubleshooting. One more thing: what would configure HEAP for server?
See if anyone has anything it will be interesting (Google is not helping much). Maybe someone has already stated this type of documentation, or thought "in my business is + or - well, it will be very useful and good.
Well now thanks to all.
Beyond that, specifics of tuning and troubleshooting techniques are best described by the documentation of the specific application server you use (informed by the results of your own performance testing). There is no universal "set the heap to n and all will be well" rule.
Thank´s a lot.
OK but there is no parameter or setting that should be followed? Something in the configuration files for the J2EE performance is the best?
No. Think about it: without knowing what your application does and how it is used how can you know what amount of memory it will need? What works for one server may bediferent on another.
And the heap? In truth I want to know is what it is and if it made a physical or logical configuration (system).
I'm not sure I really understand this question, but the "heap" is an area of memory allocated to the JVM to allow it to perform dynamic memory allocation. you define its size using JVM parameters and ultimately it is limited by the physical constraints of the memory available.
Yet even thank you.
In a J2EE server to 8 GB of memory, as a "heap" would set?
The only answer you can give to that is "it depends" followed by a long discussion of the parameters involved in performance testing and server configuration.