Facing issues with higher concurrent requests on Publisher instanceWe have applied Dispatcher caching for all static content. Post running load test we observed :- if 2 request per user are going to Publisher, it works fine.- if number of requests are more than 2/user then response time is getting drastically increased.Kindly suggest on tuning of Publisher instance to handle higher concurrent request.

Facing performance issues with HTML request being served from Publisher. As we increase Concurrency, response time start increasing drastically.The HTML has Dynamic content per user so not able to cache it on dispatcher.Please help if any other way to load this dynamic content. Read about Sling Dynamic Include. Is their any other way??

We are trying to configure NAS Storage for Multiple Publisher Instances. What we noticed is it is creating UUID file for each instance and the content in datastore is not shared across instances. Common repository, but each instance have its own data. Is it possible that they also share same data.We wanted to use NAS to achive two things:1. Save space2. Avoid Data Syncup across Publishers. If one publisher is down and brought backup again after 1/2 days it should have access to updated data with...