Delphi程序一启动占用很多内存,最小化后占内存剧减,再还原,内存增大,但始终大不到开始运行的时候那么
大,请问这是为什么?
举个例子来说:一程序启动的时候点内存5M,最小化后800K,再还原时变成1.5M,怎么也大不到5M了。 请问:在最小化窗口时,为什么内存占用率可以减少那么多,并且再次还原窗口后,内存也没有刚启动程序时占的大了?到底最小化窗口时,执行了什么清理内存的代码,可不可以把最小化时Delphi清理内存的代码单独写出来供我们使用,以减小程序内存占用率吗?
大,请问这是为什么?
举个例子来说:一程序启动的时候点内存5M,最小化后800K,再还原时变成1.5M,怎么也大不到5M了。 请问:在最小化窗口时,为什么内存占用率可以减少那么多,并且再次还原窗口后,内存也没有刚启动程序时占的大了?到底最小化窗口时,执行了什么清理内存的代码,可不可以把最小化时Delphi清理内存的代码单独写出来供我们使用,以减小程序内存占用率吗?
解决方案 »
- 如何隐藏光标
- 谁有好的图标,做程序放在按钮上的,要大点的,32*32的就可以,给我点(在线)
- 高手请进,关于COM+访问数据库.up有分人,分不够可以再加.
- 请问怎样写求最大值和求某字段平均值的sql语句?
- 谁用过ExpressQuantumGrid For Delphi6
- 开发ASP的ActiveX时一个小问题
- 加个按钮打印、打印预览TWebBrowser的内容该怎么做?
- 前阵子帮人搞的一个东西,害得我一晚没睡。源码提供下载,大家请指正~
- TreeView读取节点个数问题
- 怎样捕捉数据库在插入数据是的异常!!!!!
- 怎么用源代码制作成可以直接使用的程序
- 有人熟悉在IIS6下开发通配符过滤程序吗?
SetProcessWorkingSetSize
[code]
The SetProcessWorkingSetSize function sets the minimum and maximum working set sizes for a specified process. The working set of a process is the set of memory pages currently visible to the process in physical RAM memory. These pages are resident and available for an application to use without triggering a page fault. The size of the working set of a process is specified in bytes. The minimum and maximum working set sizes affect the virtual memory paging behavior of a process.BOOL SetProcessWorkingSetSize( HANDLE hProcess, // open handle to the process of interest
DWORD dwMinimumWorkingSetSize, // specifies minimum working set size
DWORD dwMaximumWorkingSetSize // specifies maximum working set size
);
ParametershProcessAn open handle to the process whose working set sizes will be set.
Windows NT: The handle must have PROCESS_SET_QUOTA access rights. For more information, see Process Objects.dwMinimumWorkingSetSizeSpecifies a minimum working set size for the process. The virtual memory manager attempts to keep at least this much memory resident in the process whenever the process is active.
If both dwMinimumWorkingSetSize and dwMaximumWorkingSetSize have the value 0xffffffff, the function temporarily trims the working set of the specified process to zero. This essentially swaps the process out of physical RAM memory.dwMaximumWorkingSetSizeSpecifies a maximum working set size for the process. The virtual memory manager attempts to keep no more than this much memory resident in the process whenever the process is active and memory is in short supply.
If both dwMinimumWorkingSetSize and dwMaximumWorkingSetSize have the value 0xffffffff, the function temporarily trims the working set of the specified process to zero. This essentially swaps the process out of physical RAM memory. Return ValuesIf the function succeeds, the return value is nonzero.
If the function fails, the return value is zero. Call GetLastError to obtain extended error information.ResThe working set of the specified process can be emptied by specifying the value 0xffffffff for both the minimum and maximum working set sizes.
If the values of either dwMinimumWorkingSetSize or dwMaximumWorkingSetSize are greater than the process' current working set sizes, the specified process must have the SE_INC_BASE_PRIORITY_NAME privilege. Users in the Administrators and Power Users groups generally have this privilege. For more information about security privileges, see Privileges. The operating system allocates working set sizes on a first-come, first-served basis. For example, if an application successfully sets 40 megabytes as its minimum working set size on a 64-megabyte system, and a second application requests a 40-megabyte working set size, the operating system denies the second application's request.
Using the SetProcessWorkingSetSize function to set an application's minimum and maximum working set sizes does not guarantee that the requested memory will be reserved, or that it will remain resident at all times. When the application is idle, or a low-memory situation causes a demand for memory, the operating system can reduce the application's working set. An application can use the VirtualLock function to lock ranges of the application's virtual address space in memory; however, that can potentially degrade the performance of the system.When you increase the working set size of an application, you are taking away physical memory from the rest of the system. This can degrade the performance of other applications and the system as a whole. It can also lead to failures of operations that require physical memory to be present; for example, creating processes, threads, and kernel pool. Thus, you must use the SetProcessWorkingSetSize function carefully. You must always consider the performance of the whole system when you are designing an application.
[/code]