There is no RedisGraph-specific tooling for introspecting on memory usage; I personally use Valgrind.
In some areas, deleting entities from a graph bookmarks space for reuse instead of freeing it outright, so if your deletions far outpace your creations, you might see increased memory consumption! I doubt that would account for a 7GB increase, however.
GRAPH.DELETE asynchronously marks a graph for deletion, so it’s possible that there are leaks in a workflow that calls
GRAPH.DELETE then overwrites the graph key with the bulk loader. This behavior can be overwritten by building RedisGraph with the command
make clean && make memcheck. If successful, the server log should include a line like:
156483:M 01 Feb 2021 13:13:51.022 * <graph> Graph deletion will be done synchronously.
But this approach is only recommended for debugging.