|
发表于 2014-6-19 04:51:31
|
显示全部楼层
Lazarus wrote:I would say it's unlikely to cause a performance hit.
Internally, when a consolidated element is selected in a view, TM1 finds all leaf elements under the consolidated element to determine which values to sum. Additional data being on disk, or even in memory, wouldn't affect this process, regardless of feeder flags or cached calc values.
I'm inclined to agree with both your reasoning and conclusions. However...
Lazarus wrote:I'm not convinced this additional data exists in memory, just because it has not been re-saved to disk yet.
I believe it does, at least in the session during which the deletion was done. (Not afterwards, though, I agree.)
I just obliterated all but 1 element in a dimension on a decent-sized (100 meg) cube, carefully watching the performance monitor stats both before and after for both the server and the cube. The stats were exactly the same, even after a data save (which, as I'd guessed, didn't update the .cub date and time). Not a byte was reduced from the cube, not a byte added to garbage. To get the reduction in the memory usage I had to re-start the server. During the load on restart none of the values relating to the missing elements could be loaded (as I'd mentioned earlier) and thus it had a much smaller memory footprint.
The one test that I didn't do (since I couldn't do both in the one set) was to make a data change in the cube after the deletion was done to see whether that sent all of the surplus memory to garbage. |
|