We've seen some behaviour in production environments with short lived connections where did doc records are building up. If the connection is deleted then the did_doc records aren't applicable anymore.
We need to look into this and figure out if there's a problem and if it needs a fix for this behaviour.
Also we are seeing large memory usage when we have a large amount of did:peer's in the wallet. Are the did:peer's loading into the cache? If they are they probably shouldn't be. They are static assets. Getting the from the DB isn't a big cost but storing the in memory is.
We've seen some behaviour in production environments with short lived connections where did doc records are building up. If the connection is deleted then the did_doc records aren't applicable anymore.
We need to look into this and figure out if there's a problem and if it needs a fix for this behaviour.
Also we are seeing large memory usage when we have a large amount of did:peer's in the wallet. Are the did:peer's loading into the cache? If they are they probably shouldn't be. They are static assets. Getting the from the DB isn't a big cost but storing the in memory is.