Huge memory cost using visdom server

Recently, when I am using visdom, a strange phenomenon appears that huge momory cost by the ternado server. To be specific, around 11% of 250G system memory are occupied by the visdom server.

The following shows the memory cost

The strange thing is that another visdom server (port 8098) appears to work normally. The number/size of envs in these two servers are similar. So theoretically, they should have comparable memory cost.

The only difference is the 8099 server seems to set up more parallel threads.

The following show the result of lsof -i:8099

The following show the result of lsof -i:8098

I holp we can discuss the possible reasons here, and the way to prevent such embarrassment.