<https://lavag.org/topic/6534-memory-fragmentation/#comment-38242>
<http://schema.org/text>
"QUOTE(jlokanis @ Nov 13 2007, 03:36 PM)  \n\nI saved the VI I posted in 8.2, so you should be able to look at it. This doesn't require the inplace structure and should by itself give you a big usage memory improvement. \nIf you do rethink this, then I would suggest finding a way to write the important data to file, and then be able to read the file and build a tree-friendly data structure from that. Your current architecture requires you to read and then update things, which would be difficult with File IO, so it'd only work if you find a way to simply write data to file without worrying about what's already been written. \nFor instance, if you have a property called Symbol for a tree that you want to update occasionally, then you should write the tree tag and the symbol to the file as a pair. Then if you need to update it later, you don't change what you wrote to the file the first time, but you just append a new symbol and tree tag pair to the file. When you get around to displaying the tree, you read all the messages from the file and only take the most recent messages for each tree tag. In other words, you'd read a message to update the tree symbol twice, and the second message would overwrite the first. \nThis would help you completely avoid memory allocation issues. The downside is that you have to spend a little extra time catching up when the user's ready to view the tree. \n"
<https://lavag.org/topic/6534-memory-fragmentation/?tab=comments#comment-38245>