Re: ls eat high CPU time when LANG=zh_CN.UTF-8 and LC_ALL=zh_CN.UTF-8
On Sun, Jul 10, 2016 at 04:23:03PM +0800, Huang Wen Hui wrote: > I can reproduce it on a clean 11.0-BETA1 VM. > fixed in r302916. Will merge in 2 days in stable/11 Best regards, Bapt signature.asc Description: PGP signature
Re: ls eat high CPU time when LANG=zh_CN.UTF-8 and LC_ALL=zh_CN.UTF-8
On Sun, Jul 10, 2016 at 04:23:03PM +0800, Huang Wen Hui wrote: > I can reproduce it on a clean 11.0-BETA1 VM. > > > 2016-07-09 9:03 GMT+08:00 Huang Wen Hui : > > > For some reasons, r302324 seems not include in 11.0-ALPHA6? > > > > 2016-07-09 8:52 GMT+08:00 Huang Wen Hui : > > > >> Revert back r302324, Chinese locale problem is gone. > >> > >> Cheers > >> Huang Wen Hui > >> Thanks, I can reproduce now, I'm looking into it. Bapt signature.asc Description: PGP signature
Re: ls eat high CPU time when LANG=zh_CN.UTF-8 and LC_ALL=zh_CN.UTF-8
I can reproduce it on a clean 11.0-BETA1 VM. 2016-07-09 9:03 GMT+08:00 Huang Wen Hui : > For some reasons, r302324 seems not include in 11.0-ALPHA6? > > 2016-07-09 8:52 GMT+08:00 Huang Wen Hui : > >> Revert back r302324, Chinese locale problem is gone. >> >> Cheers >> Huang Wen Hui >> >> 2016-07-05 16:50 GMT+08:00 Baptiste Daroussin : >> >>> On Tue, Jul 05, 2016 at 12:16:42PM +0800, Huang Wen Hui wrote: >>> > These 2 files can make ls suck: >>> > >>> > touch 火灾1 >>> > touch 火灾2 >>> > >>> > 2 files start with 2 same Chinese chars. >>> > >>> I cannot reproduce on my head laptop, neither on a clean 11.0-ALPHA6 >>> jail. >>> >>> I'll try on a clean 11.0-ALPHA6 VM >>> >>> Best regards, >>> Bapt >>> >> >> > ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: ls eat high CPU time when LANG=zh_CN.UTF-8 and LC_ALL=zh_CN.UTF-8
For some reasons, r302324 seems not include in 11.0-ALPHA6? 2016-07-09 8:52 GMT+08:00 Huang Wen Hui : > Revert back r302324, Chinese locale problem is gone. > > Cheers > Huang Wen Hui > > 2016-07-05 16:50 GMT+08:00 Baptiste Daroussin : > >> On Tue, Jul 05, 2016 at 12:16:42PM +0800, Huang Wen Hui wrote: >> > These 2 files can make ls suck: >> > >> > touch 火灾1 >> > touch 火灾2 >> > >> > 2 files start with 2 same Chinese chars. >> > >> I cannot reproduce on my head laptop, neither on a clean 11.0-ALPHA6 jail. >> >> I'll try on a clean 11.0-ALPHA6 VM >> >> Best regards, >> Bapt >> > > ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: ls eat high CPU time when LANG=zh_CN.UTF-8 and LC_ALL=zh_CN.UTF-8
Revert back r302324, Chinese locale problem is gone. Cheers Huang Wen Hui 2016-07-05 16:50 GMT+08:00 Baptiste Daroussin : > On Tue, Jul 05, 2016 at 12:16:42PM +0800, Huang Wen Hui wrote: > > These 2 files can make ls suck: > > > > touch 火灾1 > > touch 火灾2 > > > > 2 files start with 2 same Chinese chars. > > > I cannot reproduce on my head laptop, neither on a clean 11.0-ALPHA6 jail. > > I'll try on a clean 11.0-ALPHA6 VM > > Best regards, > Bapt > ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: ls eat high CPU time when LANG=zh_CN.UTF-8 and LC_ALL=zh_CN.UTF-8
On Tue, Jul 05, 2016 at 12:16:42PM +0800, Huang Wen Hui wrote: > These 2 files can make ls suck: > > touch 火灾1 > touch 火灾2 > > 2 files start with 2 same Chinese chars. > I cannot reproduce on my head laptop, neither on a clean 11.0-ALPHA6 jail. I'll try on a clean 11.0-ALPHA6 VM Best regards, Bapt signature.asc Description: PGP signature
Re: ls eat high CPU time when LANG=zh_CN.UTF-8 and LC_ALL=zh_CN.UTF-8
These 2 files can make ls suck: touch 火灾1 touch 火灾2 2 files start with 2 same Chinese chars. % lldb /bin/ls (lldb) target create "/bin/ls" Current executable set to '/bin/ls' (x86_64). (lldb) run Process 2185 launching Process 2185 launched: '/bin/ls' (x86_64) Enter Control+C: libc.so.7 was compiled with optimization - stepping may behave oddly; variables may not be available. Process 2185 stopped * thread #1: tid = 100261, 0x000800ff5aa7 libc.so.7`_collate_lookup [inlined] largesearch(table=) + 38 at collate.c:276, stop reason = signal SIGSTOP frame #0: 0x000800ff5aa7 libc.so.7`_collate_lookup [inlined] largesearch(table=) + 38 at collate.c:276 [opt] 273 next = (low + high) / 2; 274 p = tab + next; 275 compar = key - p->val; -> 276 if (compar == 0) 277 return (p); 278 if (compar > 0) 279 low = next + 1; (lldb) bt * thread #1: tid = 100261, 0x000800ff5aa7 libc.so.7`_collate_lookup [inlined] largesearch(table=) + 38 at collate.c:276, stop reason = signal SIGSTOP * frame #0: 0x000800ff5aa7 libc.so.7`_collate_lookup [inlined] largesearch(table=) + 38 at collate.c:276 [opt] frame #1: 0x000800ff5a81 libc.so.7`_collate_lookup(table=, t=, len=, pri=, which=, state=) + 465 at collate.c:343 [opt] frame #2: 0x000800fd80a9 libc.so.7`wcscoll_l(ws1=, ws2=, locale=) + 985 at wcscoll.c:171 [opt] frame #3: 0x000800fd4d19 libc.so.7`strcoll_l(s="火灾1", s2="火灾2", locale=0x00080124a338) + 393 at strcoll.c:101 [opt] frame #4: 0x000800fe9313 libc.so.7`qsort(a=, n=, es=, cmp=(libc.so.7`fts_compar at fts.c:966)) + 13763 at qsort.c:130 [opt] frame #5: 0x000800f25297 libc.so.7`fts_sort(sp=, head=, nitems=) + 135 at fts.c:995 [opt] frame #6: 0x000800f2638e libc.so.7`fts_children(sp=, instr=2) + 254 at fts.c:570 [opt] frame #7: 0x004030df ls`traverse(argc=, argv=, options=) + 463 at ls.c:576 [opt] frame #8: 0x00402eeb ls`main(argc=, argv=) + 2299 at ls.c:498 [opt] frame #9: 0x004020cf ls`_start + 383 2016-07-04 15:04 GMT+08:00 Baptiste Daroussin : > On Mon, Jul 04, 2016 at 02:51:46PM +0800, Huang Wen Hui wrote: > > 2016-07-04 14:41 GMT+08:00 Baptiste Daroussin : > > > > > On Mon, Jul 04, 2016 at 02:36:11PM +0800, Huang Wen Hui wrote: > > > > 2016-07-04 14:20 GMT+08:00 Baptiste Daroussin : > > > > > > > > > On Mon, Jul 04, 2016 at 11:56:36AM +0800, Huang Wen Hui wrote: > > > > > > Hi, > > > > > > On very recent CURRENT, ls can eat high CPU time when > > > LANG=zh_CN.UTF-8 > > > > > and > > > > > > LC_ALL=zh_CN.UTF-8: > > > > > > > > > > > > % uname -a > > > > > > FreeBSD mbp.gddsn.org.cn 11.0-ALPHA6 FreeBSD 11.0-ALPHA6 #121 > > > r302331M: > > > > > Mon > > > > > > Jul 4 10:47:27 CST 2016 r...@mbp.gddsn.org.cn: > > > > > /usr/obj/usr/src/sys/MACBOOK > > > > > > amd64 > > > > > > > > > > > > top show: > > > > > > 4457 hwh 1 1000 16784K 4416K CPU44 0:22 > 98.86% > > > ls > > > > > > > > > > > > any ideas? > > > > > > > > > > > Is it in all directories or only in directories with files in > chinese > > > > > characters? > > > > > > > > > Yes, the directory contain Chinese characters. > > > > > > > > > > > > > > Is it only happening when you run ls with some arguments (in > particular > > > > > -l) or > > > > > with any arguments? > > > > > > > > > I use ls -wGl > > > > > > > > > > > > > > Do you see the same if you force any other locale like en_US.UTF-8? > > > > > > > > > There is no problem if set en_US.UTF-8. > > > > > > > > > > > > > Best regards, > > > > > Bapt > > > > > > > > > > > Can you try: > > > env -i LANG=zh_CN.UTF-8 LC_COLLATE=C ls -l > > > > > > And tell me if it still happen? > > > > > No problem with this command. > > > > Ok so there might be an very inefficient code in the new chinese collation > code > I will look into it thanks a lot for reporting. > > Best regards, > Bapt > ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: ls eat high CPU time when LANG=zh_CN.UTF-8 and LC_ALL=zh_CN.UTF-8
On Mon, Jul 04, 2016 at 02:51:46PM +0800, Huang Wen Hui wrote: > 2016-07-04 14:41 GMT+08:00 Baptiste Daroussin : > > > On Mon, Jul 04, 2016 at 02:36:11PM +0800, Huang Wen Hui wrote: > > > 2016-07-04 14:20 GMT+08:00 Baptiste Daroussin : > > > > > > > On Mon, Jul 04, 2016 at 11:56:36AM +0800, Huang Wen Hui wrote: > > > > > Hi, > > > > > On very recent CURRENT, ls can eat high CPU time when > > LANG=zh_CN.UTF-8 > > > > and > > > > > LC_ALL=zh_CN.UTF-8: > > > > > > > > > > % uname -a > > > > > FreeBSD mbp.gddsn.org.cn 11.0-ALPHA6 FreeBSD 11.0-ALPHA6 #121 > > r302331M: > > > > Mon > > > > > Jul 4 10:47:27 CST 2016 r...@mbp.gddsn.org.cn: > > > > /usr/obj/usr/src/sys/MACBOOK > > > > > amd64 > > > > > > > > > > top show: > > > > > 4457 hwh 1 1000 16784K 4416K CPU44 0:22 98.86% > > ls > > > > > > > > > > any ideas? > > > > > > > > > Is it in all directories or only in directories with files in chinese > > > > characters? > > > > > > > Yes, the directory contain Chinese characters. > > > > > > > > > > > Is it only happening when you run ls with some arguments (in particular > > > > -l) or > > > > with any arguments? > > > > > > > I use ls -wGl > > > > > > > > > > > Do you see the same if you force any other locale like en_US.UTF-8? > > > > > > > There is no problem if set en_US.UTF-8. > > > > > > > > > > Best regards, > > > > Bapt > > > > > > > > Can you try: > > env -i LANG=zh_CN.UTF-8 LC_COLLATE=C ls -l > > > > And tell me if it still happen? > > > No problem with this command. > Ok so there might be an very inefficient code in the new chinese collation code I will look into it thanks a lot for reporting. Best regards, Bapt signature.asc Description: PGP signature
Re: ls eat high CPU time when LANG=zh_CN.UTF-8 and LC_ALL=zh_CN.UTF-8
2016-07-04 14:41 GMT+08:00 Baptiste Daroussin : > On Mon, Jul 04, 2016 at 02:36:11PM +0800, Huang Wen Hui wrote: > > 2016-07-04 14:20 GMT+08:00 Baptiste Daroussin : > > > > > On Mon, Jul 04, 2016 at 11:56:36AM +0800, Huang Wen Hui wrote: > > > > Hi, > > > > On very recent CURRENT, ls can eat high CPU time when > LANG=zh_CN.UTF-8 > > > and > > > > LC_ALL=zh_CN.UTF-8: > > > > > > > > % uname -a > > > > FreeBSD mbp.gddsn.org.cn 11.0-ALPHA6 FreeBSD 11.0-ALPHA6 #121 > r302331M: > > > Mon > > > > Jul 4 10:47:27 CST 2016 r...@mbp.gddsn.org.cn: > > > /usr/obj/usr/src/sys/MACBOOK > > > > amd64 > > > > > > > > top show: > > > > 4457 hwh 1 1000 16784K 4416K CPU44 0:22 98.86% > ls > > > > > > > > any ideas? > > > > > > > Is it in all directories or only in directories with files in chinese > > > characters? > > > > > Yes, the directory contain Chinese characters. > > > > > > > > Is it only happening when you run ls with some arguments (in particular > > > -l) or > > > with any arguments? > > > > > I use ls -wGl > > > > > > > > Do you see the same if you force any other locale like en_US.UTF-8? > > > > > There is no problem if set en_US.UTF-8. > > > > > > > Best regards, > > > Bapt > > > > > Can you try: > env -i LANG=zh_CN.UTF-8 LC_COLLATE=C ls -l > > And tell me if it still happen? > No problem with this command. > > Best regards, > Bapt > ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: ls eat high CPU time when LANG=zh_CN.UTF-8 and LC_ALL=zh_CN.UTF-8
On Mon, Jul 04, 2016 at 02:36:11PM +0800, Huang Wen Hui wrote: > 2016-07-04 14:20 GMT+08:00 Baptiste Daroussin : > > > On Mon, Jul 04, 2016 at 11:56:36AM +0800, Huang Wen Hui wrote: > > > Hi, > > > On very recent CURRENT, ls can eat high CPU time when LANG=zh_CN.UTF-8 > > and > > > LC_ALL=zh_CN.UTF-8: > > > > > > % uname -a > > > FreeBSD mbp.gddsn.org.cn 11.0-ALPHA6 FreeBSD 11.0-ALPHA6 #121 r302331M: > > Mon > > > Jul 4 10:47:27 CST 2016 r...@mbp.gddsn.org.cn: > > /usr/obj/usr/src/sys/MACBOOK > > > amd64 > > > > > > top show: > > > 4457 hwh 1 1000 16784K 4416K CPU44 0:22 98.86% ls > > > > > > any ideas? > > > > > Is it in all directories or only in directories with files in chinese > > characters? > > > Yes, the directory contain Chinese characters. > > > > > Is it only happening when you run ls with some arguments (in particular > > -l) or > > with any arguments? > > > I use ls -wGl > > > > > Do you see the same if you force any other locale like en_US.UTF-8? > > > There is no problem if set en_US.UTF-8. > > > > Best regards, > > Bapt > > Can you try: env -i LANG=zh_CN.UTF-8 LC_COLLATE=C ls -l And tell me if it still happen? Best regards, Bapt signature.asc Description: PGP signature
Re: ls eat high CPU time when LANG=zh_CN.UTF-8 and LC_ALL=zh_CN.UTF-8
2016-07-04 14:20 GMT+08:00 Baptiste Daroussin : > On Mon, Jul 04, 2016 at 11:56:36AM +0800, Huang Wen Hui wrote: > > Hi, > > On very recent CURRENT, ls can eat high CPU time when LANG=zh_CN.UTF-8 > and > > LC_ALL=zh_CN.UTF-8: > > > > % uname -a > > FreeBSD mbp.gddsn.org.cn 11.0-ALPHA6 FreeBSD 11.0-ALPHA6 #121 r302331M: > Mon > > Jul 4 10:47:27 CST 2016 r...@mbp.gddsn.org.cn: > /usr/obj/usr/src/sys/MACBOOK > > amd64 > > > > top show: > > 4457 hwh 1 1000 16784K 4416K CPU44 0:22 98.86% ls > > > > any ideas? > > > Is it in all directories or only in directories with files in chinese > characters? > Yes, the directory contain Chinese characters. > > Is it only happening when you run ls with some arguments (in particular > -l) or > with any arguments? > I use ls -wGl > > Do you see the same if you force any other locale like en_US.UTF-8? > There is no problem if set en_US.UTF-8. > Best regards, > Bapt > ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: ls eat high CPU time when LANG=zh_CN.UTF-8 and LC_ALL=zh_CN.UTF-8
On Mon, Jul 04, 2016 at 11:56:36AM +0800, Huang Wen Hui wrote: > Hi, > On very recent CURRENT, ls can eat high CPU time when LANG=zh_CN.UTF-8 and > LC_ALL=zh_CN.UTF-8: > > % uname -a > FreeBSD mbp.gddsn.org.cn 11.0-ALPHA6 FreeBSD 11.0-ALPHA6 #121 r302331M: Mon > Jul 4 10:47:27 CST 2016 > r...@mbp.gddsn.org.cn:/usr/obj/usr/src/sys/MACBOOK > amd64 > > top show: > 4457 hwh 1 1000 16784K 4416K CPU44 0:22 98.86% ls > > any ideas? > Is it in all directories or only in directories with files in chinese characters? Is it only happening when you run ls with some arguments (in particular -l) or with any arguments? Do you see the same if you force any other locale like en_US.UTF-8? Best regards, Bapt signature.asc Description: PGP signature
ls eat high CPU time when LANG=zh_CN.UTF-8 and LC_ALL=zh_CN.UTF-8
Hi, On very recent CURRENT, ls can eat high CPU time when LANG=zh_CN.UTF-8 and LC_ALL=zh_CN.UTF-8: % uname -a FreeBSD mbp.gddsn.org.cn 11.0-ALPHA6 FreeBSD 11.0-ALPHA6 #121 r302331M: Mon Jul 4 10:47:27 CST 2016 r...@mbp.gddsn.org.cn:/usr/obj/usr/src/sys/MACBOOK amd64 top show: 4457 hwh 1 1000 16784K 4416K CPU44 0:22 98.86% ls any ideas? Huang Wen Hui ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
