| Subject: | Re: Namei cache? | |
|---|---|---|
| From: | Bruce Evans (bd...@zeta.org.au) | |
| Date: | Dec 9, 1997 9:44:45 pm | |
| List: | org.freebsd.freebsd-current | |
Refine Search
| From | Sent On | Attachments |
|---|---|---|
| Geoff Mohler | Dec 9, 1997 9:27 am | |
| Poul-Henning Kamp | Dec 9, 1997 10:55 am | |
| Geoff Mohler | Dec 9, 1997 12:13 pm | |
| Poul-Henning Kamp | Dec 9, 1997 1:20 pm | |
| Bruce Evans | Dec 9, 1997 9:44 pm |
| Subject: | Re: Namei cache? | |
|---|---|---|
| From: | Bruce Evans (bd...@zeta.org.au) | |
| Date: | Dec 9, 1997 9:44:45 pm | |
| List: | org.freebsd.freebsd-current | |
In current there is little you can do.
You can try to increase:
kern.maxvnodes debug.wantfreevnodes
I see what these values currently are, but what are my boundaries and rules I have to follow in changing them..IE: stay in 4096 incrememnts..dont go above 99999...etc.
You'll run out of memory if you set them too high...
Add 10% or so at a a time, let it run for a day before you judge the result...
In current there is little you can do.
Setting kern.maxvnodes has no effect unless debug.wantvnodes is set to 0. Setting debug.wantvnodes to 0 just gives kern.maxvnodes the old function of debug.wantvnodes. Setting debug.wantvnodes has very little effect. It just controls how fast the system ramps up to peak vnode allocation. This is bogus of course. The man page is more bogus/incomplete.
Bruce

