Sometimes I notice my PC being very very slow... The Chrome Task Manager (SHIFT+ESPACE) shows that "On device" IA is taking 300% of the CPU (laptop with only low-perf Intel integrated GPU). I can barely type text in an input box: 1 second delay after each keypress.
Disabling the option "On device AI" in the same way than on OP's screenshot doesn't solve this issue: this "On device" process still comes back again and again and I have to kill it manually.
This is probably just Chrome redownloading the weights. But there is a fringe possibility that the local model is getting hijacked for inference, or even more sci-fi, that it’s being corrupted by some sort of rogue global botnet.
When I read about Chrome shipping local weights in every computer I can’t help but be reminded of the Great Cannon, where a MITM code injection by China caused end-user browsers to launch a DDOS on GitHub back in 2015. What could an AI adversary do with a fraction of Chrome’s local models, I wonder.
> I don't know what is going on with this guy's computer, but Chrome AI features do not use "hundreds of GBs per month".
What else, going on with this guy's computer, would cause that volume of traffic to immediately stop as soon as he "disabled everything on that settings page"?
It may not be happening to you if you've got all that crap enabled, but that doesn't mean it wasn't happening to him. Companies love to single out subsets of their userbase and secretly experiment on them. When something goes wrong users get gaslighted by other people who say "I never see that happen!" or "It works fine for me!". Who the hell knows what Google and their AI was doing on this guy's computer. I'd put more trust in a random web developer on the internet than I'd trust Google.
"Hundreds of GB per month" is, at least, 70KB/s, which should be pretty easy for anyone to observe. So is your Chrome doing it?
My hypothesis is this guy installed so many shady ad blockers and VPNs that were using his rig as a proxy, and the cessation of such traffic, whether permanent or temporary, was purely coincidental.
The problem here is without a deep dive you just don't know. Google likes A/Bing the shit out of their software. Google loves setting all kinds of different options that may have to be replicated exactly to get the same behavior.
This isn't like support back in the old days where you just look at your software and find the bug, you have to replicate the environment to see what's up.
Every app and site I use that has AI integration is slower (Chrome, VSCode, the keyboard on my Android, Bank-Apps). And routing a bunch of stuff into their sites new chat feature which is so buggy that what should be trivial tasks take much longer.
Fast used to be a feature.
I thinking this is just a wave of hot-patch-slop that will pull back soon-ish, if the feedback loop works. Many times the folk making these decisions are so far removed from customer complaints, the there is any complaint (because many users don't bother)
I've always said Chrome became the new IE, especially when you consider that Google and some web devs build sites that only work in Chrome, even though Firefox can run them, I've seen too many sites tell me I should be on Chrome instead, giving me flashbacks to IE in the 2000s...
Chrome is obscenely fast and it has never been faster. The only thing that can touch it is Safari, a browser that co-evolves with its own hardware platform. Blink and V8 have closed what should have been an unbridgeable performance gap with Safari, and the third place browser isn't in the same galaxy as the top two.
I have another problem with Chrome AI features.
Sometimes I notice my PC being very very slow... The Chrome Task Manager (SHIFT+ESPACE) shows that "On device" IA is taking 300% of the CPU (laptop with only low-perf Intel integrated GPU). I can barely type text in an input box: 1 second delay after each keypress.
Disabling the option "On device AI" in the same way than on OP's screenshot doesn't solve this issue: this "On device" process still comes back again and again and I have to kill it manually.
Did someone experience the same?
I don't know what is going on with this guy's computer, but Chrome AI features do not use "hundreds of GBs per month".
This is probably just Chrome redownloading the weights. But there is a fringe possibility that the local model is getting hijacked for inference, or even more sci-fi, that it’s being corrupted by some sort of rogue global botnet.
When I read about Chrome shipping local weights in every computer I can’t help but be reminded of the Great Cannon, where a MITM code injection by China caused end-user browsers to launch a DDOS on GitHub back in 2015. What could an AI adversary do with a fraction of Chrome’s local models, I wonder.
https://en.wikipedia.org/wiki/Great_Cannon
> I don't know what is going on with this guy's computer, but Chrome AI features do not use "hundreds of GBs per month".
What else, going on with this guy's computer, would cause that volume of traffic to immediately stop as soon as he "disabled everything on that settings page"?
It may not be happening to you if you've got all that crap enabled, but that doesn't mean it wasn't happening to him. Companies love to single out subsets of their userbase and secretly experiment on them. When something goes wrong users get gaslighted by other people who say "I never see that happen!" or "It works fine for me!". Who the hell knows what Google and their AI was doing on this guy's computer. I'd put more trust in a random web developer on the internet than I'd trust Google.
"Hundreds of GB per month" is, at least, 70KB/s, which should be pretty easy for anyone to observe. So is your Chrome doing it?
My hypothesis is this guy installed so many shady ad blockers and VPNs that were using his rig as a proxy, and the cessation of such traffic, whether permanent or temporary, was purely coincidental.
Your take is 'probably' correct.
The problem here is without a deep dive you just don't know. Google likes A/Bing the shit out of their software. Google loves setting all kinds of different options that may have to be replicated exactly to get the same behavior.
This isn't like support back in the old days where you just look at your software and find the bug, you have to replicate the environment to see what's up.
OK but the OP provided zero evidence. Chrome has chrome://net-export/ for a reason. Show us logs.
> The problem here is without a deep dive you just don't know.
Without knowing, you don't accuse.
"Don’t take my word for it." - agreed
you can disable the AI crap in chrome/chromium by setting policy file.
(Linux)
Chrome: `/etc/opt/chrome/policies/managed/disable_ai.json`
Chromium: `/etc/chromium/policies/managed/disable_ai.json`
```
{
}```
Every app and site I use that has AI integration is slower (Chrome, VSCode, the keyboard on my Android, Bank-Apps). And routing a bunch of stuff into their sites new chat feature which is so buggy that what should be trivial tasks take much longer.
Fast used to be a feature.
I thinking this is just a wave of hot-patch-slop that will pull back soon-ish, if the feedback loop works. Many times the folk making these decisions are so far removed from customer complaints, the there is any complaint (because many users don't bother)
I'm old enough to remember a commercial for Chrome that measured a page render against a potato cannon: https://www.youtube.com/watch?v=EYmjoW4vIX8
there was a time where it used to be the defining feature of chrome.
chrome used to be the simplest browser, with a minimal interface that was lean and fast...
It's hard to believe that Chrome was the obvious choice for power users back then. I miss the blue title bar
That was when user experience was the defining feature of apps.
Now it's IE6 on cocaine.
I've always said Chrome became the new IE, especially when you consider that Google and some web devs build sites that only work in Chrome, even though Firefox can run them, I've seen too many sites tell me I should be on Chrome instead, giving me flashbacks to IE in the 2000s...
Chrome moves too fast to be the new IE. The entire web dev industry was frozen in ember accommodating IE6 for years. It was excruciating.
I’m no fan of a Google monopoly but I still prefer where we are today to those days.
Chrome is obscenely fast and it has never been faster. The only thing that can touch it is Safari, a browser that co-evolves with its own hardware platform. Blink and V8 have closed what should have been an unbridgeable performance gap with Safari, and the third place browser isn't in the same galaxy as the top two.
Chromes mostly open source...
Point to the specific AI features which are wasting bandwidth and quantify how much.
I wonder if this ties into a strategy of selling their 3gig google fiber plans.
https://ungoogled-software.github.io/
It doesn't have the AI features, which improves the product quite a bit.