Personally, I am not a fan of micro-optimization, but filterEdges goes through every edges that fetched so maybe little bit optimization on this method would be necessary.
Through benchmark, I see lots of CPU cycle is waisted on Graph.toHashKey and just checking for exclude/include.
after profile through visualvm, filterEdges on Graph contains unnecessary check which use many CPU cycle.
point to improve on Graph.filterEdges is following(develop branch).
Personally, I am not a fan of micro-optimization, but filterEdges goes through every edges that fetched so maybe little bit optimization on this method would be necessary.
Through benchmark, I see lots of CPU cycle is waisted on Graph.toHashKey and just checking for exclude/include.