Design constrain checks touch A LOT of stuff: usually things have several classes attached to them and check need to be performed on union or intersection of cl

Design constrain checks touch A LOT of stuff: usually things have several classes attached to them and check need to be performed on union or intersection of class-related data. Place and route, even for 2D PCB, also touches a lot of stuff - it needs to access constraints, at the very least. In our case, constraint system had to return data to PCB real-time router in under 100us, for several tens of millions of different classes of constraints. I cannot see how you can speak of singular accesses in this context. Or "single-digit as many" accesses. Now I'll leave conversation. We clearly have different view on almost everything, including, but not limited to "huge multipliers".