![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
Factor Three
Jan. 14th, 2016 11:09 pmIt's being like that today. I had intended, at some point, to rewrite the entity data handling on the new Server architecture. Sadly, the current entity data handling is causing our consolidation to run out of memory, so I really need to rewrite it now.
The good news is that -- after a brief false start -- I have figured out how to structure things so that they work in a fashion that's similar to everything else on the Server that requires locking. The locking itself still needs some work for a clustered environment, but that's something that can be replaced in one swell foop once we get everything else straightened out. Since we're not yet running clustered, the current locking will do for the moment.
The amusing thing is that I have finally found a place where using a WeakHashMap is the right answer. :)
I'll still be cleaning this up tomorrow morning, but there is a non-train light at the end of the tunnel.
The good news is that -- after a brief false start -- I have figured out how to structure things so that they work in a fashion that's similar to everything else on the Server that requires locking. The locking itself still needs some work for a clustered environment, but that's something that can be replaced in one swell foop once we get everything else straightened out. Since we're not yet running clustered, the current locking will do for the moment.
The amusing thing is that I have finally found a place where using a WeakHashMap is the right answer. :)
I'll still be cleaning this up tomorrow morning, but there is a non-train light at the end of the tunnel.