Page daemon frees but doesn't examine?

Ask a Question related to Sun Solaris, Design and Development.

  1. #1

    Default Page daemon frees but doesn't examine?

    Hi,

    Just a bit curious at the output of vmstat -s.

    ......
    174293 pages paged out
    ......
    0 pages examined by the clock daemon
    0 revolutions of the clock hand
    174131 pages freed by the clock daemon


    Just wondering how the clock daemon pages out pages "without"
    examining the them? - Anyone have an explanation?

    Thanks,

    Asif.
    Asif Guest

  2. Similar Questions and Discussions

    1. Net::Daemon::SSL
      Hi I'm now making a simple script using Net::Daemon::SSL. However, the code listed below(which appeared in...
    2. daemon??
      Who would I need to speak to about making a product that involves the little devil? It is not a software item, but instead it is a material object?...
    3. Daemon proc run on a port, kill daemon and cannot restart on same port for 10 minutes.
      Unix is AIX 4.3 The daemon is a license manager which runs for an application. Killing the daemon is fine. (using the 'kill -9 <pid>')...
    4. FTP Daemon...
      Hi All, Has anyone written/used a simple ftp daemon, if so, can you please me to the CPAN modules you used (i haven't found anything that really...
    5. Daemon
      Hello, In my ASP application I have a new requirement to email users a notification on a weekly basis if certain conditions are met. Is it...
  3. #2

    Default Re: Page daemon frees but doesn't examine?

    Asif <asif.sadiq@uk.neceur.com> wrote:
    > Hi,
    > Just a bit curious at the output of vmstat -s.
    What OS?
    > .....
    > 174293 pages paged out
    > .....
    > 0 pages examined by the clock daemon
    > 0 revolutions of the clock hand
    > 174131 pages freed by the clock daemon
    > Just wondering how the clock daemon pages out pages "without"
    > examining the them? - Anyone have an explanation?
    My guess is that this is Solaris 8 or later and that the changes in the
    VM handling are not entirely reflected in the vmstat -s messages.

    It used to be that all pages were freed by the page scanner, after being
    examined and found to be not used recently enough. With large amounts
    of memory, this is just too slow, and too time consuming. It limits the
    amount of I/O the machine is capable of.

    With Solaris 8 and up, the kernel is now capable of freeing memory that
    is no longer needed directly, without the page scanner becoming involved
    at all.

    My suspicion is that the 174131 pages are somehow pages in the past that
    would have been freed only through the actions of the page scanner, but
    now do not need it. The 'vmstat -s' code is just pulling values from
    the kernel, and the text hasn't been rewritten to modify statements that
    are no longer strictly true.

    It's just a WAG, but I'll bet it's close.

    --
    Darren Dunham [email]ddunham@taos.com[/email]
    Unix System Administrator Taos - The SysAdmin Company
    Got some Dr Pepper? San Francisco, CA bay area
    < This line left intentionally blank to confuse you. >
    Darren Dunham Guest

Posting Permissions

  • You may not post new threads
  • You may post replies
  • You may not post attachments
  • You may not edit your posts

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 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139