Printable View
When the app's memory usage is about 30M bytes, it runs fast.
But if it allocates a continuous big block of memory such as 100M bytes, while the cpu's load is constant and the physical memroy is enough. It will run much slower.
for example
What's the reason?Code://MyDoc.h
class MyDoc : public CDocument
{
//just allocate a big blcok of memory,but it won't be used
//as a result , the app will run much slower
double m_d[1024*1024*25];
}
Thanks!
When you say the app runs slowly what exactly do you mean? Slowly as in running the app in one shot is slow, OR slowly as in application is used over a period of time and it runs slowly during that time?
If you have enough physical memory AND if you are not using that big block of memory, then over time, one should not expect any performance degradation. I say over time because initially the process working set may be trimmed because of that big allocation, and some pages that would have been used might have been evicted, and then paged back in, but over time (like seconds) things should fall into equilibrium. Your big block of memory ** may ** be paged out and pages in use would stay in memory.
The app will run slowly during it's whole lifecycle.Quote:
Originally Posted by UnderDog
But I found that if allocates memory by the way as below
These won't slow down the app.Code:method 1:
class CMyDocument:public CDocument
{
double * m_pD;
CMyDocument(){m_pD=new double[1024*1024*25];}
~CMyDocument(){delete[] m_pD;}
};
or
method 2:
class CMyDocument:public CDocument
{
static double m_D[1024*1024*25];
};
So I think that it's the way which MFC processing CDocument object cause the app runs slower.
Because neither method 1 nor method 2 make the CMyDocument object's size become enormous.But the way discussed in the topic article do.
Are you making copies/multiple objects of MyDoc?
No. The app was built as single document/view frame.Quote:
Originally Posted by UnderDog
But even if I made copies objects of MyDoc. The memory will be allocated all the same.