**System Information**
Operating system: Windows-10-10.0.18362-SP0 64 Bits
Graphics card: GeForce GTX 980 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 445.75
**Blender Version**
Broken: version: 2.83 (sub 15), branch: master, commit date: 2020-04-24 15:23, hash: `rBa8441fc90086`
Worked: Same happens in 2.82 / previous versions.
**Short description of error**
Adding a Mirror Modifier and using an empty or another object to mirror across, causes slow viewport performance, if SubSuf Modifier is also in the stack and enabled. .
**Exact steps for others to reproduce the error**
1. Add a Mirror Modifier, and choose another object / empty as a mirror position/target to use.
2. Add a subSurf Modifier before or after the Mirror modifier, and turn up the viewport subD Levels so is more dense.{F8497811}
# Open file
3. Tried to move/rotate that object and notice very sluggish performance.
4. Disable subSurf Display in viewport, and notice much higher performance/updates.
5. Enable subSurf Display , but then Clear mirror modifier object / use object itself as a mirror (no mirror target) and notice much better viewport performance.
A workaround, is to always disable subSurf display in viewport when transforming objects with this setup, I suppose. But I still wonder if there's some optimizations/things to do, to fix this/improve for future? Maybe this will be part of highpoly mesh viewport perf for 2.9?
{F8494647}# Move Suzanne - Notice performance
# Remove Mirror Object from mirror modifier
# Move Suzanne - Performance much better
You can apply subdiv modifier, it shouldn't have an effect.