I’m going to have to return my mini, I got the i7 with 16gigs but using it on a 4K monitor in scaled mode with Photoshop is significantly slower that my MBP 2016 15”. Zoom is lagging like crazy and every pixel manipulation tool is slow as hell.
Just a warning for the people looking to use it in photoshop.
That is concerning. Are you sure there aren't just a lot of background processes going on like indexing?
But the most important thing to check is how it behaves at different resolutions. Running it in the way you are, I think, means it is rendering and 5120x2880 and then scaling to 4K. This, I guess will be a little bit more taxing than driving a native 5K panel - depending on how efficient the scaling part is.
By contrast if you run at 1920x1080 (equivalent) which would be native 2x for your display, the initial rendering will be less demanding (3840x2190), plus no scaling will be required. If that is also poor, then it sounds, to me, as if something else is hogging Photoshop resources.
A real test would be to plug into a native 2560x1440 (or lower) display to see what affect that has.
I currently run a 2011 quad mini with HD3000 plugged in to both a 2560x1440 and 1920 x 1200 displays. The UI animations are a little choppy, but i don't believe it to actually slow down the responsiveness of apps. I am hoping, of course that the 2018 mini will be a lot better...but you have me concerned in case I upgrade to a 4K or 5K display in the future. It seems it may require an eGPU.
Another point. A colleague has a 2017 MBPro connected to a 2560x1440 display and that also lags a lot with UI animations on the external screen. And that has a dGPU...I'm not sure why.
[doublepost=1541931855][/doublepost]
I’ve only noticed it in Photoshop (and animations between spaces could be a tiny bit choppy), a 3000x2000 image, nothing special at all.
2x on 4K is 1920 and that’s way too low for everything else even if it would work.
The question is: does running at a lower res improve the response? If it doesn't then it suggests the problem is something else, not (just) the GPU.