Microsoft Office Tutorials and References
In Depth Information
Capacity Planning
When the ECS saves a copy of the workbook to the local workbook disk cache, the workbook disk size is
essentially the same size as when the Excel client saved the workbook to disk.
Each ECS requires a workbook disk cache. The quantity and size of the workbooks being loaded by the
ECS dictate how much physical disk space is required to support all of the workbooks. As workbooks get
updated by workbook authors, new versions of the workbooks are saved to the workbook disk cache. The
outdated versions of the workbooks remain in the workbook disk cache until evictions are triggered by
the ECS, which occurs when the maximum size of the workbook disk cache is reached or the ECS process
is restarted.
Memory Size
Each ECS has an associated w3wp.exe process, also referred to as the ECS process . The size of the ECS
process is indicated by the w3wp.exe private bytes performance counter. You can use the Windows Task
Manager or Performance Monitor to see the size of the ECS process in real time. The Memory Usage
column in the task manager represents the ECS process size.
Follow these steps to use the Task Manager to view the ECS process size:
1.
Use the Windows tasklist.exe utility to identify the w3wp.exe process that is associated with the
ECS. From a cmd.exe window, enter tasklist /FI “MODULES eq xlsrv.dll” .
The output will look like this:
Image Name PID Session Name Session# Mem Usage
========================= ======== ================ =========== ============
w3wp.exe 3232 RDP-Tcp#3 0 95,440 K
2.
Click Start
Run.
3.
Enter taskmgr and click OK.
4.
Select the Process tab and then click the Image Name column to sort the list of processes.
5.
Scroll the list to locate the w3wp process ID (PID) that was returned by the tasklist command
you executed in step 1. (In the output shown as an example in step 1, the w3wp PID associated
with the ECS was 3232.)
In addition to saving a copy of the workbook to the ECS workbook disk cache, the ECS also loads the
workbook into memory. This is the w3wp process memory that you can monitor by watching the private
bytes, as described in the previous steps. Each workbook that gets loaded into memory impacts the ECS
process size, and after the workbook is loaded into memory, it is referred to as the base workbook .
Consider the workbooks listed in the previous table, and assume that the workbooks do not yet exist in the
ECS workbook memory cache (the base workbook does not yet exist). When the open workbook call is
made for each workbook, the size of the ECS process increases as the workbook gets loaded into memory.
The following table shows the amount of ECS memory consumed by each of the three base workbooks as
a percentage of the workbook’s disk size. The amount of memory needed for workbooks depends on the
content of the workbook, which encompasses data, formatting, and the Excel features contained in the
workbook.
Search JabSto ::




Custom Search