Sometimes a vRouter may show memory usage larger than what was expected. One of the common suspicion is the flow numbers. The problem is that flow table changes dynamically and is difficult to trace the historical information.
The 'flow_count' counter in this introspect URL can be used to reveal maximum flow entries that the vRouter ever experienced.
user@router:~$ curl localhost:8085/Snh_SandeshFlowTableInfoRequest <SandeshFlowTableInfoResp type="sandesh"> <flow_count type="u64" identifier="1"> 3558 <total_added type="u64" identifier="2"> 209398936 <total_deleted type="u64" identifier="3"> 209395523 <max_flows type="u64" identifier="4"> 1645978 #<--- <table_list type="list" identifier="5"> <list type="struct" size="4"> <SandeshFlowTableInfo> <index type="u32" identifier="1"> 0 <count type="u32" identifier="2"> 920 <total_add type="u64" identifier="3"> 53027164 <total_del type="u64" identifier="4"> 53026244 <freelist_count type="u64" identifier="5"> 415080 <SandeshFlowTableInfo> <index type="u32" identifier="1"> 1 <count type="u32" identifier="2"> 896 <total_add type="u64" identifier="3"> 52942164 <total_del type="u64" identifier="4"> 52941268 <freelist_count type="u64" identifier="5"> 415104 <SandeshFlowTableInfo> <index type="u32" identifier="1"> 2 <count type="u32" identifier="2"> 868 <total_add type="u64" identifier="3"> 53264805 <total_del type="u64" identifier="4"> 53263937 <freelist_count type="u64" identifier="5"> 414132 <SandeshFlowTableInfo> <index type="u32" identifier="1"> 3 <count type="u32" identifier="2"> 874 <total_add type="u64" identifier="3"> 53337256 <total_del type="u64" identifier="4"> 53336382 <freelist_count type="u64" identifier="5"> 415126 <more type="bool" identifier="0"> false