@CCiCC I am glad it worked.
it is good you can use pages correctly now, for whatever reason Chromium 106 enabled that option, which was off in 105, maybe for a reason like messing with some GPU acceleration, it’s hard to keep up with updates like that for sure, I am sure not many would notice these types of changes that are so internal.
About the % usage between Edge or Brave, less doesn’t necessarily mean better, it is good it is using the GPU if the acceleration is there, you would have to see if Brave CPU consumption is less, so it uses less CPU but more GPU which should be the best way and maybe Brave is using more fps when dealing with the GPU acceleration.
And the only way to see fps count clearly is by using something like https://webglsamples.org/, which is not the same as the floor plans, but it is the only way to see if Edge is really more efficient while using less GPU.
You will notice Chromium will limit FPS to 60, so if you want to unlock FPS and temporary go beyond 60, you can always run browsers with:
--disable-frame-rate-limit --disable-gpu-vsync
@Chocoholic exactly, “common troubleshooting technique” a temporary test, a way to see if the GPU (like in this case) is causing more issues than good, but usually GPU information is going to be a better place to start than going with the “disable it” right away, without knowing what brave://gpu says, they don’t even know if GPU acceleration is working properly.
And also mostly the problem is people using is as a permanent solution because ‘it works’ , yeah maybe it works in a 720p youtube video with a decent CPU, but if we talk about more heavy stuff like this floor plans website or a webgl or game or something or 4k or something then no.
Yes, GPU matters, an old GPU as you say, might be slower in some stuff, but never to work worst than CPU would, since CPU has way less cores, any decent new GPU with DX11 support should handle things okay. If not they would use DX9 which barely supports any Hardware Acceleration features.
Some old or not so old GPUs might be even blacklisted so it is not even going to use the GPU anyway, so you have to enable the #ignore-gpu-blocklist flag. So sometimes people think they are even using GPU acceleration when they aren’t.
So there are many variables to just say “turn it off” as the first anything, and to be honest, people don’t really compare the before and after, sometimes it is more a ‘placebo’ effect because maybe they were using CPU already and they think it is performing better.
Few weeks ago I helped someone to troubleshoot GPU and with just GPU page information I told him that his GPU was not able to do true decoding of vp9 format which is what Youtube uses, but it was like a hybrid solution so it wasn’t completely done by CPU, his GPU only supported full acceleration up to H265.
So that’s the most important part too, to check GPU and see what it even supports.
Of course I don’t expect many people to know Out-of-process 2D canvas rasterization, was enabled by default, but it was pretty easy to figure out by looking at Edge and Brave GPU pages, so the obvious test was to turn it off.
Hardware acceleration is better, look at 3D rendering, in many cases CPU will be more stable, won’t have problems with memory since it will use computer’s memory and not the GPU memory which is less, and have more features and all, which is the reason why big studios still use CPU and have their big rendering farms, but the truth is GPU is faster and it can work in many many ways, so imagine GPU for websites which will never be as heavy as a 3D renderer.
Of course GPU acceleration is kind of bad, especially since it is tied to JS and other web technologies, if you run a youtube 1080p video in mpv vs browser, mpv will use like 1% CPU, while no a browser it might use 9% for example, of course many times it has to do with the Audio service too, so that’s why I say things are heavier in Web Browsers, many variables and not just simple hardware acceleration.
Anyway! that’s why I always mention turning hardware acceleration off is a bad advice, not because it is, it is a valid troubleshooting solution but I know people will use it as a permanent solution instead of truly fix their GPU issue, and running things only on CPU seems okay but it is not good for so many things.
it fixed the lag/stuttering issue when I am turning on 2 floor plans at the same time. But one thing I have noticed is the range of usage in my gtx1050ti using brave with this fixed is about 5% to 20%, But in edge is only 3 to 7%. I think this is another problem right now. But most importantly, my problem has been fixed. Thank you so much. 
I think the users who are concerned and know better (like those you pointed out) would definitely not be satisfied with that solution or even with suggesting that option be a permanent “fix”.