We have a knowledge article that mentions the following notes about the session replication:

we recommend keeping the amount of data stored in the session as small as possible. Storing a lot of data in the session objects can have an impact on the performance of the session replication. (For example, storing a large size of the object as the session attribute, storing many numbers of objects as the session attributes, or accessing mutable session attributes frequently.) Make sure to examine load testing with your real-world application to determine a proper balance of data storage and performance to effectively use sessions.

Can we improve our official product documentation JBoss EAP 7.3 Development Guide - 6.1. Session Replication (or JBoss EAP 7.3 Performance Tuning Guide) to include similar notes to the above?