formance of the controller is majorly judged on 2 factors which include the number of flows that the controller can setup in a second and the time taken for setting up the flow. The factors mentioned above are extremely under the bulge when extra controllers are to put into action. Consider when routers in production Software Defined Networking throws out more flows than the capacity of the controller, the number of controller's requirement must be increased (Ashton and Metzler, 2012). The setting up of the flow can be done in two major fashions, either before or during Downloaded: 4/15/2022 9:44:49 AM Nova Southeastern University IP Address: 137.52.76.29 The Heart and Brain of SDN the course i.e. proactively or reactively. The former occurs before the message is pinged at the switch, this means that the switch is already aware of where to or what to do with the packet once it arrives. This gives an unprecedented advantage in setting up the network and there is no restriction on the number of packets that can be handled by the controller per minute or second. In the perfect world, then controller should popularize the flow tables to the highest capacity possible. But that happens in perfect world, not in a real one. The latter set up fashion of reactive setting up happens when the switch (which runs on OpenFlow protocol) gets the message that fits no match with any of the entries in the flow table and hence it is sent to the controller which decides what will be the fate of the packet. Once the controller. Which is the Supreme Court in this scenario gives its orders, to the high court, i.e. the switch as to how to process the flow it is entered into the cache of OpenFlow switch and the Supreme Court also decides the lifetime of the cache. The major ornaments governing the affect the time of slow setup are the power of processing of the OpenFlow switches and alongside the input output performance and processing of the controller itself. Consider a controller that is written in low level programming language will b