Currently DefaultProfileCache is going to grow the more profiles we get in runtime. This could lend into memory issues.
Through the introduction of comms, we are going to fetch more profiles from peers. We need an implementation to dispose the unused profiles, for those users who has been disconnected, moved out from our room, etc.
DefaultProfileCache already has some methods for removing profiles from the map, however we need to hook this calls into the domain's flow. Also, we should properly implement DefaultProfileCache.Unload(...) method.
Another thing worth mentioning is that DefaultProfileCache.UpdateProfilingCounter() is wrongly implemented. We should fix this line, since the profile intentions are not the current profiles:
Currently
DefaultProfileCache
is going to grow the more profiles we get in runtime. This could lend into memory issues. Through the introduction of comms, we are going to fetch more profiles from peers. We need an implementation to dispose the unused profiles, for those users who has been disconnected, moved out from our room, etc.DefaultProfileCache
already has some methods for removing profiles from the map, however we need to hook this calls into the domain's flow. Also, we should properly implementDefaultProfileCache.Unload(...)
method. Another thing worth mentioning is thatDefaultProfileCache.UpdateProfilingCounter()
is wrongly implemented. We should fix this line, since the profile intentions are not the current profiles: