Re: Sv: copy-on-write optimized faults

1999-10-31 Thread Bill Fumerola
On Sun, 31 Oct 1999, Louis A. Mamakos wrote: > And my mine... I get zero COW optimized faults. THE E-MAIL EXPLICITLY SAID ONLY TO POST IF YOU HAVE MORE THEN 0 FAULTS I hope one day the people who don't read this list carefully miss something really important and it eats your system as a result.

Re: Sv: copy-on-write optimized faults

1999-10-31 Thread Louis A. Mamakos
-write faults 0 copy-on-write optimized faults 7306697 zero fill pages zeroed 4185272 zero fill pages prezeroed 1801 intransit blocking page faults 8604076 total VM faults taken 8804200 pages freed 20 pages freed by daemon 2300440 pages freed by exiting processes 16937

Re: Sv: copy-on-write optimized faults

1999-10-31 Thread Andre Oppermann
ed by the page daemon 7730 pages reactivated 867915 copy-on-write faults 0 copy-on-write optimized faults 1295449 zero fill pages zeroed 1106142 zero fill pages prezeroed 56 intransit blocking page faults 2560858 total VM faults taken 2706144 pages freed 2 pages f

Re: Sv: copy-on-write optimized faults

1999-10-31 Thread sthaug
> I get high numbers too: > > FreeBSD mailtoaster1.pipeline.ch 3.2-STABLE FreeBSD 3.2-STABLE #3: Sun > Jun 13 20:31:43 CEST 1999 [EMAIL PROTECTED]:/usr/src/sys > /compile/mailtoaster1 i386 Read the original message. It says: > > I would appreciate it if people running -current would run a

Re: Sv: copy-on-write optimized faults

1999-10-31 Thread Iceman
Leif Neland wrote: > > > I would appreciate it if people running -current would run a "vmstat -s" > > and tell me if they see a NON-ZERO value for copy-on-write optimized > > faults. About six months ago, I implemented a simpler and more general > > optimiz

Re: copy-on-write optimized faults

1999-10-30 Thread Jonathan M. Bresler
sr/src/sys/compile/ASPEN > i386 > Aspen:[210] vmstat -s [snip] >111374 cpu context switches >22 pages reactivated > 8410 copy-on-write faults > 1264 copy-on-write optimized faults please ignoire this erro...i got to get away from the keyboard toni

Re: copy-on-write optimized faults

1999-10-30 Thread Jonathan M. Bresler
i gets lots of "copy-on-write optimized faults". bu tthis may be a corner case. just rebooted my box. its used for ppp with nat aliasing and is in the middle of a cvsup follwed by 'cvs update -PAd'. the box is fairly weak40MB in a AMD 5x86-133MHz. Aspen:[208] uptime

Sv: copy-on-write optimized faults

1999-10-30 Thread Leif Neland
> > 2062637 copy-on-write optimized faults < > [cut] > > > I must have something configured wrong, or??? > > No, but you didn't read Allan's original posting, the change only applied to > -CURRENT, your box is running -STABLE ... > OKOKOKOK! Don&#

Re: copy-on-write optimized faults

1999-10-30 Thread Jesper Skriver
On Sat, Oct 30, 1999 at 06:54:07PM +0200, Leif Neland wrote: > > > > I would appreciate it if people running -current would run a "vmstat -s" > > and tell me if they see a NON-ZERO value for copy-on-write optimized > > faults. About six months ago, I impl

Sv: copy-on-write optimized faults

1999-10-30 Thread Leif Neland
> I would appreciate it if people running -current would run a "vmstat -s" > and tell me if they see a NON-ZERO value for copy-on-write optimized > faults. About six months ago, I implemented a simpler and more general > optimization at an earlier "fork in the road&q

Re: copy-on-write optimized faults

1999-10-29 Thread Brian Fundakowski Feldman
ew days. At this frequency, the cost of deciding > whether or not to apply the optimization on every copy-on-write fault > is greater than what is saved those 26 times it is applied. I get about 1.5PPM optimized COW faults: 7734278 copy-on-write faults 12 copy-on-write optimized fault

Re: copy-on-write optimized faults

1999-10-29 Thread Alan Cox
On Sat, Oct 30, 1999 at 12:47:40AM +0200, Bernd Walter wrote: > > 307625181 copy-on-write faults > 26 copy-on-write optimized faults Thanks to Bernd and everyone else who has responded. Unless someone reports a case where the old "optimization" gets applied more

RE: copy-on-write optimized faults

1999-10-29 Thread Alexander N. Kabaev
vmstat -s reports these numbers on my computer: 3649151 copy-on-write faults 1 copy-on-write optimized faults On 29-Oct-99 Alan Cox wrote: > I would appreciate it if people running -current would run a "vmstat -s" > and tell me if they see a NON-ZERO value for copy-on

Re: copy-on-write optimized faults

1999-10-29 Thread Bernd Walter
On Fri, Oct 29, 1999 at 02:47:43PM -0500, Alan Cox wrote: > I would appreciate it if people running -current would run a "vmstat -s" > and tell me if they see a NON-ZERO value for copy-on-write optimized > faults. About six months ago, I implemented a simpler and more genera

Re: copy-on-write optimized faults

1999-10-29 Thread Ollivier Robert
81472 pages reactivated 9492270 copy-on-write faults 29 copy-on-write optimized faults <<<<<<<<< 18936477 zero fill pages zeroed 10633059 zero fill pages prezeroed 17337 intransit blocking page faults 51673604 total VM faults taken 643

Re: copy-on-write optimized faults

1999-10-29 Thread Alan Cox
9 pages examined by the page daemon > 404278 pages reactivated > 3711393 copy-on-write faults >199653 copy-on-write optimized faults > 69735710 zero fill pages zeroed > 11909269 zero fill pages prezeroed >253956 intransit blocking page faults > 198695719 tot

Re: copy-on-write optimized faults

1999-10-29 Thread Jesper Skriver
On Fri, Oct 29, 1999 at 02:47:43PM -0500, Alan Cox wrote: > I would appreciate it if people running -current would run a "vmstat -s" > and tell me if they see a NON-ZERO value for copy-on-write optimized > faults. About six months ago, I implemented a simpler and more genera

copy-on-write optimized faults

1999-10-29 Thread Alan Cox
I would appreciate it if people running -current would run a "vmstat -s" and tell me if they see a NON-ZERO value for copy-on-write optimized faults. About six months ago, I implemented a simpler and more general optimization at an earlier "fork in the road". (In effect, I a