To address your questions, I would recommend submitting a ticket with Technical Support to go through your situation. In general, you should not be responsible for clearing memory. The garbage disposal of IIS and Memory Manager should be clearing out memory as the execution of the function is complete. The assumption of a Cube View rendering not exceeding 1 GB is not entirely a correct assumption. It all depends on the amount of data pulled into cache and then inserted into a data table. Each data record in a database takes 3,200 bytes. If you have 1 million data records from the result of the Cube View definitions, then you will use 3.2 GB of memory just for the data records not including the additional memory for the new object of a data table. Every Cube View can be wildly different so I can't give you a definitive answer on any of this. It would be a good idea to meet with Technical Support to run through all of this. The memory not releasing could be a concern but we won't know unless Technical Support gets involved to troubleshoot. OneStream has a lot of memory intensive processes. Cube Views being one of them. 16 GB's on a server is ok for general development but not optimal for a Production environment. 16 GB's of memory can be consumed very quickly depending on the process, data volumes, number of large data tables in memory, etc.
Thanks TonyToniTone
In the past the tech support team was not terribly interested in having our memory dumps. Moreover, a memory dump of 16 GB that demonstrates a problem is pretty unwieldy, even after you are able to download it and open it with a tool like in WinDbg. I was just going to watch counters, and take some smaller memory dumps after running a few cubeviews and triggering the garbage collection.
Ideally it would be possible to confirm a memory problem before 3 or 5 GB. If necessary I could work on creating an artificial repro with tiny cubeviews. I just wanted to know what to look for, to determine whether things were "leaking" or just "caching". (I know that this distinction can sometimes be based on lots of factors.)
Based on your response, it sounds like you have no knowledge of FDX-specific memory issues. I will hold off on assuming that there is a problem for now.... The only reason for my suspicion is based on the behavior I noticed, and the requirement for IIS to be reset every night. Yes, our production servers do have quite a lot more RAM (32 or 64 I think).
