TM1 Forum

Hi
It urgent for me please help me.
Actually I have total available space in my F: drive 179 GB and free space is 98 GB.
And running in the 11GB Data model in my F:\ drive so now I plan to run the 5 GB data model in the same drive so in this scenario would you think that is required additional drive for this or I can run in the same drive itself?

As basic arithmetics shows, you do not need additional drive space to run your model. However, TM1 is an in-memory database engine and during runtime all of the metadata and data is loaded into RAM. So first and foremost you need to make sure you have sufficient RAM for your model.
Also, please note that how much disk space a model occupies is not in direct correlation with how much memory it uses up when loaded and running. And additional RAM will be needed for every user session and things like view generation (not to mention advanced tasks like reordering dims in a cube). There are some rough guidelines on server sizing in the official documentation available online.

mincharug.shulft wrote:Hi
It urgent for me please help me.

{Sigh} Yup, well pretty much every other post you've made has also been "urgent", no reason why this one shouldn't be.

(See also: "Wolf, Boy Who Cried")

mincharug.shulft wrote:Actually I have total available space in my F: drive 179 GB and free space is 98 GB.
And running in the 11GB Data model in my F:\ drive so now I plan to run the 5 GB data model in the same drive so in this scenario would you think that is required additional drive for this or I can run in the same drive itself?

As QML has pointed out, size on disk and size in memory have nothing whatsoever to do with each other and you haven't indicated which measurement you're referring to when you cite the size of your model. Obviously if you're citing a data directory size then as QML said it's a pretty basic exercise in arithmetic. if you're citing the memory size then that's irrelevant; all you need to know is the file size which you can discover pretty easily by just doing a data save. However the other factors to take into consideration are:
- How much logged data entry is going to be done on this model; and
- Will the transaction logs also be stored on that drive? This is something that you should have gotten a feel for in the development cycle.

My rough rule of thumb is to try to keep a 20% buffer of free space at all times. Others may vary on this, but since a server WILL go down if it can't write to disk, it's probably worthwhile being conservative than pushing the resources right to their limits.