Why do all the proposed avenues of future investigation, and all of the current comments on this thread, focus on voodoo instead of the far more likely explanation that the display driver is just stomping on the memory of the network interface? If there's software anywhere in a system, 99% of the time that's the problem.
A good way to think about Wayland is the screen manager brought to you by the people who thought xrandr, Mesa, Cairo, the Linux FireWire stack, and freetype were good things. If you come in with appropriate expectations you’ll be amazed that any of it works at all.
Is you think it over for a bit you’ll realize that the real Linux graphics protocol is Android SurfaceFlinger. Wayland is like five orders of magnitude less popular.
Part of search quality is serving nothing when there are no results. Putting a bunch of irrelevant Pinterest pages in the results, just because there are no good results, isn’t good for users.
It has literally nothing to do with K8s. An equally suitable title would have been "Debugging network stalls on the Intel Xeon processor" or "Debugging network stalls on planet Earth".
This does not really have anything to do with either kubernetes or networks. If your computer is busy, it won't be able to process packets. Accessing certain kernel stats via proc, sys, or other special files may be really expensive. For example /proc/pid/smaps of a running mysqld takes 2 seconds on a computer I happen to have on hand. Sometimes when you have many cores it is expensive to produce some of the fields of /proc/pid/stat because the kernel has to visit numerous per-cpu data structures. /proc/pid/statm is better for this reason, if it contains what you are looking for.
TL;DR reading kernel stats can take a long time and cost a lot of CPU cycles. It costs more for more containers, and more on bigger machines.
Can we talk about the ethics of just reposting, verbatim, a paper written by others, but with an advertisement inserted between every paragraph? How did that become OK?
I wonder how this sounds to people who live in, say, Switzerland, where it is very mountainous, snows frequently, and literally nobody drives a truck, and even the cars are not AWD.
I mean, I _know_ how it sounds because I am one of those people. But I wonder how Americans think this sounds.
Nextdoor is bad because your neighbors are bad people, and it only takes a few to wreck it. Somewhere on your block lives a life-long racist, a chemtrail crackpot, and an insufferable busybody. Normally these people hide but for some reason they think Nextdoor is their safe space.
How do various mail clients talk to their respective backends? I.e. what does iOS Mail use to talk to iCloud? The GMail iOS app speaks a bespoke binary protocol to Google's servers, not IMAP.
This does not really apply to individual Americans. The American carbon footprint boils down to driving and meat. Individual decisions made by super-consumers can be impactful.
The ability of local agencies to just post to your feed has been a feature of Nextdoor for years. They can also close their posts to discussion, which is pretty irritating.
Yeah the title should be "unionfs: a kernel feature having nothing whatever to do with containers, and some ways to use it" but I guess that's too long :-) . Problem is there is not some central marketing department for Linux that can even tell us what "containers" means. There are lots of people who think they are "using containers" who do not use this style of mount, and there are lots of people using this style of mount who do not consider themselves container users.
The guy has been in office for 10 months. The projected 2019 GDP growth is less than actual 2018 growth. Latest available unemployment rate was the same as the rate from the year prior. Which aspect of the Brazilian economy strikes you as considerably better?
They are not very competitive for the price. They are about 50% slower than same-priced quad core Core i3 CPUs on Chrome Octane 2 benchmarks, 25% slower on video encoding, etc. AMD is free-riding the good reviews of their latest parts by giving these APUs very similar model numbers. In reality these are obsolete parts.
I hope people realize these are 1st-generation Zen CPUs that are Not Very Fast(tm), not the respectable Zen2 parts you've been reading good things about. AMD's marketing is very confusing right now. There are not any Zen2 APUs.
The bike stuff was basically breaking even when it was Motivate. The real tragedy here will be if Lyft bought Motivate just so they could mismanage it into non-existence.
1) Intel has per-core frequency and voltage control. To the extent that AVX-512 inhibits higher clock speeds that effect is local to the core or cores on which AVX-512 is active, and only those cores.
2) Not all AVX-512 instructions have this effect. `vpermb` for example does not.
3) Some other AVX instructions that are not AVX-512 have this effect. Also anything else that makes a core hot has this effect.
4) Most importantly, Cannon Lake microarch and later don't have this effect.
Look I'm not arguing about which CPU is better. I'm arguing that taking the geometric mean of a bunch of completely unrelated benchmarks doesn't make any sense. There are clearly workloads in this very article where a cheaper part is better, sometimes even a cheaper AMD part.
So aside from your irrelevant comments about AVX2 being about even between the two parts, what is a reasonable explanation for the second chart on page 4 of the article, assuming you can bother yourself to go read it. Their analysis seems to be essentially that if the Intel part wasn't 300% faster, then the AMD part would be 15% faster. But it is a fact that the Intel part is really three times faster on this benchmark, because of AVX-512. The only reason to include the chart with AVX disabled is to fit the article into a prejudiced narrative.