In addition to cycles, I suggest gathering TLB miss rates. eBPF isn't magical and any maps of significant size may pollute your virtual address translation caches. The last time someone asked me to profile eBPF at work, over 90% of the cycle time was attributable to page table walks, and this also had severe collateral impact on the applications.
It's pretty wild that 99% of participants came from Instagram, Facebook, or Tiktok. It never escaped that bubble? The other platforms, Reddit, YouTube, word of mouth only amounted to 1%?
Redis uses jemalloc by default, if I recall correctly, but its hostility to the way systems actually work arises from the way that it forks, then changes one bit on every page in the entire virtual space, which causes a lot of kernel work to support copy-on-write by blowing up huge pages into smaller pages. That's what happens when your program is antagonistic to the way the machine actually works.
Linux also has support for it but it is up to the distribution, or the user, to enable or disable it. The whole discourse was poisoned years ago when the author of Redis told everyone to disable THP on Linux, but this was caused by Redis being a poor program, not by THP being a poor feature. Unfortunately, even though the Redis project finally removed their document about this, many people still carry this bias.
One of the drawbacks of relying on the virtual memory subsystem is large page tables, that the machine has to manage on your behalf, and that pollute (or at least occupy) caches. That is another reason why Go, like all other software, benefits significantly if you adjust your Linux boxes to use huge pages, or larger-than-default pages, or ARM contiguous page bits, or whatever other features your platform offers to make virtual address translation more efficient. It is unfortunate that Linux usually comes out of the box with all of these post-286 features disabled.
Sure, with LSE. But you have to target LSE and get a system that actually contains it, i.e. not the default compiler flags and not the original AWS Graviton.
The combination of "I have an idea for changing one of the fundamental experiences of modern life" and "my website is obnoxious and hostile" didn't really work for me.
Whether the allocator calls are "naive" or not depends entirely on the allocator in use. If you need thread/core locality and batching you can get that by replacing global new/delete functions with a decent allocator.
Twenty years ago this would have been wrong with a kernel of truth. Today, it's just wrong. There were chips that integrated all this but they weren't that popular in the West and ultimately nobody cared.
Adjudicating whether an individual is eligible to vote is not and has never been the domain of any federal agency. It is categorically none of their business. The only federal intervention in elections that the Constitution permits is for the executive branch, traditionally through the Department of Justice, to ensure that states are not improperly preventing voters from voting, via the 15th, 19th, 24th, and 26th Amendments.
I only wanted to clarify that you must have implied that this statement applies among people who don't like Google, but whatever their reasons, those people are few. In aggregate, Google has a strong reputation and is one of the most well-liked businesses on Earth. It is on par with Cheerios. Disliking Google for "creepy stalker" reasons is not a mainstream thing.
Yeah those are pretty weird questions. I suggest you may have been spending too much time online. If you ever come across someone marketing property as the ultimate in Libertarian dirt, I would carefully investigate what liberties have been taken with it prior (dumping out New Jersey sewage trains, for example).
It's nice to have a better UX the the USDA WSS offers, but I feel that this hides too much information. If I click, I am getting soil information at a point, but that might be a minor component and doesn't tell me about the overall area of interest. Also, as a Californian I feel that is irrelevant bordering on useless to display the non-irrigated capability class, as everyone irrigates. Looking at a parcel I am intimately familiar with, it is "4 of 8" but it is class 1 irrigated farmland, prime land of high value.
If I understand the literature correctly, there is no strong evidence in favor of collagen as a dietary supplement outside of a dose just before weight lifting, because without the exertion the amino acids in blood simply don't reach tendons and ligaments.
Users are complicit. Why did this user install the update? Were they suffering from an issue it supposedly solves? My six-year-old Honda has never had a software update, and in any case "OTA" updates can only be initiated by the user.