summaryrefslogtreecommitdiff
path: root/open_issues/system_stats.mdwn
blob: ce34ec095e1e655d1d827078fe3f58a104fbe038 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
[[!meta copyright="Copyright © 2012, 2013 Free Software Foundation, Inc."]]

[[!meta license="""[[!toggle id="license" text="GFDL 1.2+"]][[!toggleable
id="license" text="Permission is granted to copy, distribute and/or modify this
document under the terms of the GNU Free Documentation License, Version 1.2 or
any later version published by the Free Software Foundation; with no Invariant
Sections, no Front-Cover Texts, and no Back-Cover Texts.  A copy of the license
is included in the section entitled [[GNU Free Documentation
License|/fdl]]."]]"""]]

[[!tag open_issue_documentation]]There should be a page listing ways to get
system statistics, how to interpret them, and some example/expected values.


# IRC, frenode, #hurd, 2012-11-04

    <mcsim> Hi, is that normal that memory cache "ipc_port" is 24 Mb already?
      Some memory has been already swapped out.
    <mcsim> Other caches are big too
    <braunr> how many ports ?
    <mcsim> 45922
    <braunr> yes it's normal
    <braunr> ipc_port              0010      76   4k    50  45937 302050
      24164k       4240k
    <braunr> it's a bug in exim
    <braunr> or triggered by exim, from time to time
    <braunr> lots of ports are created until the faulty processes are killed
    <braunr> the other big caches you have are vm_object and vm_map_entry,
      probably because of a big build like glibc
    <braunr> and if they remain big, it's because there was no memory pressure
      since they got big
    <braunr> memory pressure can only be caused by very large files on the
      hurd, because of the limited page cache size (4000 objects at most)
    <braunr> the reason you have swapped memory is probably because of a glibc
      test that allocates a very large (more than 1.5 GiB iirc) block and fills
      it
    <mcsim> yes
    <braunr> (a test that fails with the 2G/2G split of the debian kernel, but
      not on your vanilla version btw)


## IRC, frenode, #hurd, 2013-01-26

    <braunr> ah great, one of the recent fixes (probably select-eintr or
      setitimer) fixed exim4 :)