Re: RELENG_4 -> 5 -> 6: significant performance regression

Kris Kennaway a écrit :
On Thu, Apr 27, 2006 at 08:26:06PM +0200, ml@xxxxxxxx wrote:
Kris Kennaway a ?crit :
On Thu, Apr 27, 2006 at 05:08:11PM +0300, Dmitry Pryanishnikov wrote:


options QUOTA
This definitely effects performance on 6.x since it makes your
filesystem giant-locked, which may also interfere with your network
processing.
Why would QUOTA affect performance more on 6.x than 4.x ? I would like to understand because i think a system cannot be secure without QUOTA

It makes filesystem writes acquire Giant, which blocks other kernel
code that needs to also acquire Giant. When the need to acquire Giant
was removed from the mainstream UFS code in 6.0 it was an enormous
performance improvement.

Thanks for your anwser, but i'm not sure i understand... You wrote that Giant is needed in 6.0 and now you write it has been removed.

So is it removed for 6-STABLE ? 6.1-rc ? Since i already use 6.x boxes, and i do have performance issues, i would upgrade to the right version immediatly

R.
_______________________________________________
freebsd-stable@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscribe@xxxxxxxxxxx"

Relevant Pages

  • Re: RELENG_4 -> 5 -> 6: significant performance regression
    ... This definitely effects performance on 6.x since it makes your ... which may also interfere with your network ... It makes filesystem writes acquire Giant, ... was removed from the mainstream UFS code in 6.0 it was an enormous ...
    (freebsd-stable)
  • Re: Running the network stack without Giant -- change in default coming
    ... > to allow the network stack to run in parallel on multiple processors ... > currently unsafe without the Giant lock turned on. ... > configuration for testing out the impact of disabling Giant on MP ...
    (freebsd-current)
  • Running the network stack without Giant -- what to try and when
    ... As many of you have seen from status reports, e-mails, bug reports, etc, ... the FreeBSD Project has been working for some time on getting the network ... without the Giant lock, and we're ready for more people to start running ... - While we've been doing pretty heavy testing in MPSAFE configurations, ...
    (freebsd-current)
  • Removing NET_NEEDS_GIANT: first patch
    ... This source code declaration was used by optionally compiled components to declare a strict requirement for Giant, and forced Giant over the entire network stack. ... retrieving revision 1.13 ... diff -u -r1.13 amrr.c ...
    (freebsd-arch)
  • Removing NET_NEEDS_GIANT: first patch
    ... This source code declaration was used by optionally compiled components to declare a strict requirement for Giant, and forced Giant over the entire network stack. ... retrieving revision 1.13 ... diff -u -r1.13 amrr.c ...
    (freebsd-current)