Hi @kolli_sandeep , I believe you are talking about Secondary Namenode and not the Standby Namenode on a Non-HA cluster. If so, the functionality of the Secondary Namenode would be to perform the checkpointing of the fsimage with the new edits.
The Secondary NameNode does require some memory to hold the data structures and objects necessary for merging the edits log and the FsImage. However, it does not load the entire FsImage into memory at once. As such, I would suggest keeping the heap to atleast 2x times the fsimage fpr smooth functioning.