Ask a Question related to Sun Solaris, Design and Development.
-
Asif #1
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
-
Net::Daemon::SSL
Hi I'm now making a simple script using Net::Daemon::SSL. However, the code listed below(which appeared in... -
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?... -
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>')... -
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... -
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... -
Darren Dunham #2
Re: Page daemon frees but doesn't examine?
Asif <asif.sadiq@uk.neceur.com> wrote:
> Hi,What OS?> 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 daemonMy guess is that this is Solaris 8 or later and that the changes in the> Just wondering how the clock daemon pages out pages "without"
> examining the them? - Anyone have an explanation?
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



Reply With Quote

