自己先来一个找到的解决方案:
盒盖使用 mbp

来源如下:
I had the exact same issue. The problem is that Chrome is defaulting to using the integrated GPU instead of using the eGPU. For some reason, if the integrated GPU has a connected active display, Chrome will always prefer this instead of any eGPU.

You can observe this by going to chrome://gpu and seeing the available GPUs, and that Chrome has selected the integrated GPU.

The solution for this is stupidly simple, but annoying that there isn't a Chrome config to avoid this. The solution is to just shut the lid of the laptop when using an external display. This puts the laptop into "clamshell mode" which effectively "unplugs" the internal laptop display.

Once this is done, starting Chrome will result in it selecting the next GPU with an active display, which will be the eGPU. Check chrome://gpu to see if this is the case. Once Chrome has started, you can re-open the laptop lid, and Chrome will continue to use the eGPU even with the internal display being active.

Unfortunately if you are using a setup with a machine using purge-nvda, then clamshell mode is broken. This was the case for me and I was stuck using laggy Chrome.

I just recently tried using a fix for clamshell mode when using purge-nvda, discussed here:
https://egpu.io/forums/builds/MacBook-pro-15-retina-mid-2012-razer-core-x-with-rx-580-and-functional-sleeping-waking-up-and-brightness-control/
I followed the instructions on that build to fix clamshell mode, which worked and as a result I now have Chrome using the eGPU and have a super smooth experience.

如果可以不盒盖的方案来关闭内置显示器,请帮忙补充