Re: kern.sched.quantum: Creepy, sadistic scheduler
On Wed, Apr 04, 2018 at 09:32:58AM -0400, George Mitchell wrote: > On 04/04/18 06:39, Alban Hertroys wrote: > > [...] > > That said, SCHED_ULE (the default scheduler for quite a while now) was > > designed with multi-CPU configurations in mind and there are claims that > > SCHED_4BSD works better for single-CPU configurations. You may give that a > > try, if you're not already on SCHED_4BSD. > > [...] > > A small, disgruntled community of FreeBSD users who have never seen > proof that SCHED_ULE is better than SCHED_4BSD in any environment > continue to regularly recompile with SCHED_4BSD. I dread the day when > that becomes impossible, but at least it isn't here yet. -- George Indeed 4bsd is better in my case aswell. While for some unknown to me reason ule performed a bit better in the 10.x series than before, in 11.x it again is in my case not usable. Mouse freezes for around half a second with even frequency by just moving it around in x11. Using 4bsd instead makes the problem go away. I'm actually very happy that ule became worse again because going back to 4bsd yet again also gave improved performance from other dreadfully slow but (to me) still useful programs, like darktable. With 4bsd, when adjusting shadows and highlights it is possible to see what I do when moving sliders. With ule it has never been better than waiting 10-20-30 seconds to see where it was able to read a slider position and update display, when working on images around 10500x10500 greyscale. It's not single cpu/single core either: CPU: AMD FX(tm)-6300 Six-Core Processor (3817.45-MHz K8-class CPU) -- Eivind ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Locale problem updating 10.3 to 11.1
On Wed, Feb 21, 2018 at 07:16:49AM -0500, Brandon Allbery wrote: > A locale mapping is basically a lookup table (with complications for things > like ß). A single-byte lookup table will be 256 entries, each holding one > or more (because of combining characters) Unicode codepoints representing > the mapping from the locale character set to the underlying common > character set (Unicode). (There may also be a reverse lookup table for > mapping Unicode codepoints to locale codepoints.) That's fine, it doesn't make my life miserable such as it would when directly using multibyte character sets, as long as it doesn't negatively affect performance. > Without this, every program would have to deal directly with every possible > character set. Or only handle what one cares about. > (Complications include things like: depending on encoding/locale details, > German lowercase ß will uppercase to either SS or ???. While German is not my main language, I've never seen a situation where an uppcase variant of ß would make sense, though I understand the example. > And that's one of the > simpler ones; for some locales, things can get *really* weird. Not to > mention fun stuff like Arabic having 4 representations of every character: > initial, medial, final, standalone.) Complications I don't want or need, nicely points out what I dislike about unicode, although I can understand some os wanting to support it, to be useful in more situations. -- Eivind ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Locale problem updating 10.3 to 11.1
On Wed, Feb 21, 2018 at 01:03:01AM -0500, Brandon Allbery wrote: > On Tue, Feb 20, 2018 at 6:08 PM, Eivind Nicolay Evensen < > eivi...@terraplane.org> wrote: > > > However, since it was mentioned in a note starting with > > "Add support for unicode collation" I most likely didn't even read it > > since I'll never touch unicode. > > > > If you ever use anything other than LANG=C, you *are* touching Unicode. Well, I don't see multibyte characters with 8859-1, and multibyte is what I don't tolerate. I didn't even know that unicode could be single-byte character only sets. -- Eivind ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Locale problem updating 10.3 to 11.1
On Mon, Feb 19, 2018 at 09:11:29AM +0100, Eivind Nicolay Evensen wrote:
> On Mon, Feb 19, 2018 at 12:33:26AM +0100, Trond Endrestøl wrote:
> > On Mon, 19 Feb 2018 00:02+0100, Eivind Nicolay Evensen wrote:
> >
> > > Hello.
> > >
> > > After upgrading from 10.3 to 11.1 by building source (as of r329364),
> > > I experienced some problems that seems to be related to locale.
> > >
> > > Using
> > > > echo $LANG -- $LC_CTYPE
> > > no_NO.ISO8859-1 -- no_NO.ISO8859-1
> >
> > That's nb_NO.ISO8859-1.
> > nb for norsk bokmål.
>
> Interesting, I had not noticed any nb_* in freebsd and can no longer
> remember how I found no_NO. However, on 10.3 they seem to be the same:
>
> > ls -ld /usr/share/locale/n{o,b}*ISO*
> drwxr-xr-x 2 root wheel 512 11 jan 2017 /usr/share/locale/nb_NO.ISO8859-1
> drwxr-xr-x 2 root wheel 512 11 jan 2017 /usr/share/locale/nb_NO.ISO8859-15
> drwxr-xr-x 2 root wheel 512 11 jan 2017 /usr/share/locale/no_NO.ISO8859-1
> drwxr-xr-x 2 root wheel 512 11 jan 2017 /usr/share/locale/no_NO.ISO8859-15
>
> > diff -urN /usr/share/locale/n{o,b}_NO.ISO8859-1
>
>
> I'll recheck if they differ in 11.1.
And indeed, there's nothing called no_NO any more in 11.1.
Thanks for the hint. It's much appreciated. Problem is solved by
using nb_NO.ISO8859-1 instead.
This part of "20151108" in UPDATING should probably have been enough
of a clue for me:
Due to a bug in install(1) it is recommended to remove the ancient
locales before running make installworld.
However, since it was mentioned in a note starting with
"Add support for unicode collation" I most likely didn't even read it
since I'll never touch unicode.
Regards
--
Eivind
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Locale problem updating 10.3 to 11.1
On Mon, Feb 19, 2018 at 12:33:26AM +0100, Trond Endrestøl wrote:
> On Mon, 19 Feb 2018 00:02+0100, Eivind Nicolay Evensen wrote:
>
> > Hello.
> >
> > After upgrading from 10.3 to 11.1 by building source (as of r329364),
> > I experienced some problems that seems to be related to locale.
> >
> > Using
> > > echo $LANG -- $LC_CTYPE
> > no_NO.ISO8859-1 -- no_NO.ISO8859-1
>
> That's nb_NO.ISO8859-1.
> nb for norsk bokmål.
Interesting, I had not noticed any nb_* in freebsd and can no longer
remember how I found no_NO. However, on 10.3 they seem to be the same:
> ls -ld /usr/share/locale/n{o,b}*ISO*
drwxr-xr-x 2 root wheel 512 11 jan 2017 /usr/share/locale/nb_NO.ISO8859-1
drwxr-xr-x 2 root wheel 512 11 jan 2017 /usr/share/locale/nb_NO.ISO8859-15
drwxr-xr-x 2 root wheel 512 11 jan 2017 /usr/share/locale/no_NO.ISO8859-1
drwxr-xr-x 2 root wheel 512 11 jan 2017 /usr/share/locale/no_NO.ISO8859-15
> diff -urN /usr/share/locale/n{o,b}_NO.ISO8859-1
I'll recheck if they differ in 11.1.
> > ls emitted question mark for Norwegian characters (æøå), the menu
> > and title fonts in fvwm2 displayed unknown to me symbols except for
> > certain capital letters and yet other programs like the worker filemanager
> > truncated filenames at the first Norwegian letter.
> >
> > I had to revert to 10.3 because of this but if anybody has some clues
> > what may be the reason for this, I'd appreciate it.
>
> --
> Trond.
> ___
> freebsd-stable@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
--
Eivind
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Locale problem updating 10.3 to 11.1
Hello. After upgrading from 10.3 to 11.1 by building source (as of r329364), I experienced some problems that seems to be related to locale. Using > echo $LANG -- $LC_CTYPE no_NO.ISO8859-1 -- no_NO.ISO8859-1 ls emitted question mark for Norwegian characters (æøå), the menu and title fonts in fvwm2 displayed unknown to me symbols except for certain capital letters and yet other programs like the worker filemanager truncated filenames at the first Norwegian letter. I had to revert to 10.3 because of this but if anybody has some clues what may be the reason for this, I'd appreciate it. Regards -- Eivind ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
