Server Technology PPNT Manuel d'utilisateur Page 76

  • Télécharger
  • Ajouter à mon manuel
  • Imprimer
  • Page
    / 83
  • Table des matières
  • DEPANNAGE
  • MARQUE LIVRES
  • Noté. / 5. Basé sur avis des utilisateurs
Vue de la page 75
Chapter 8 | Optimizing your FileMaker Server deployment 76
Monitoring FileMaker Server
Monitoring the server is important for recognizing and preventing problems.
1 When users report a problem, such as a system crash or very slow performance, you need
good monitoring tools to determine what caused the problem.
1 By analyzing future hardware needs, taking baseline readings when monitoring a situation, or
gaining a better understanding of the server’s health, you can prevent future problems.
Monitoring performance in Windows
To monitor FileMaker Server in Windows, you can use a tool called Performance Monitor, also
known as perfmon. With the perfmon tool, you can examine how applications that are running
affect your computer's performance, including the memory used, disk access time, and log
statistics on different processes. While some log information shows obvious bottlenecks or stress
points, much of the information might require more detailed analysis. With a little experience, you
can recognize common stress points.
Note To use perfmon, you must have local Administrators group or equivalent privileges in
Windows. For more information about using perfmon, see Windows Help and Support.
There are five logs that can help you monitor performance in Windows:
1 Processor. Logs the processor activity and idle times. Select % Processor Time as the
primary indicator of processor activity and to display the average percentage of busy time. To
view the time the processor is idle, select % Idle Time.
1 Network Interface Counter (NIC). Captures bytes sent and received over each network
adapter, the length of the output packet queue (in packets), and the errors for inbound and
outbound packets.
1 Memory. Records the amount of physical memory immediately available for allocation to a
process or for system use. The log also records the Cache Bytes for Memory\System Cache,
cache faults, page faults, the number of read operations, and the pages written to disk.
1 Process. Logs statistics on processes, including time, reading and writing rate, page faults,
thread count, virtual address space, and the current size, in bytes, of the memory that this
process has allocated.
1 Disk. Captures the disk read time, the disk write time, the percentage of time the disk was idle,
the number of outstanding requests, and the split input and output to the disk.
Note The Windows Event Viewer contains the Application log and the System log, which are
useful for understanding how the server is
performing. These can provide insight into activity at
the user, system, and service level.
Reviewing the performance logs
By default the performance logs show you real time statistics of specific counters. To display the
performance logs, open Administrative Tools > Performance Monitor, then navigate to
Monitoring Tools > Performance Monitor.
Vue de la page 75
1 2 ... 71 72 73 74 75 76 77 78 79 80 81 82 83

Commentaires sur ces manuels

Pas de commentaire