Different Maximum server memory across Availability Replicas I have a scenario in SQL Server 2014 AlwaysOn High Availability where other services are running in one of the Secondary read-only replicas.

These services obviously demand additional memory. Is there any good practice or specific reason why SQL Server should have the same memory configuration across different replicas?
That’s due to fact it (SECONDARY) has to serve same level of work load as PRIMARY. I.e. when PRIMARY is memory intensive for 32GB, and SECONDARY limits to 24GB in the incident when it’s become PRIMARY it could perform same as primary the impact (8GB Memory) could be in various factors


Additional connections might not established 
Existing requests might be slower 
Log redo could be backlogged 
Etc..