Abstract: Systems and methods for dynamic core assignment for virtual machines in public cloud environments include steps of initially booting up a software package for a virtual node in a cloud-based system, wherein the software package includes N processes each configured to operate on one of N cores, N is an integer; determining a configuration of the virtual node based on communication in the cloud-based system; responsive to a first configuration, proceeding the booting up and configuring the N processes to each operate on one of N cores; and, responsive to a second configuration, rebooting for improved performance, and subsequent to the rebooting, configuring the N processes to so that at least one process is operated on at least two of the N cores and so that at least one of the N processes is omitted, improving performance.

Abstract: A network device may receive a packet flow, and may identify an application associated with the packet flow. The network device may determine that packets associated with the application are not to be encrypted using a security protocol. The network device may store a rule that indicates that the packets are not to be encrypted using the security protocol based on determining that the packets are not to be encrypted using the security protocol. The rule may include network layer information or transport layer information associated with the packet flow, and may exclude application layer information associated with the packet flow. The network device may transmit, based on the rule, the packets without using the security protocol to encrypt the packets.

Abstract: A device may receive a packet associated with a flow and may assign a flow identifier to the flow. The device may generate a first flow record based on a first template. The first flow record may include the flow identifier and a first quantity of fields determined based on the first template. The device may export the first flow record. The device may generate a second flow record, including the flow identifier, based on a second template and after exporting the first flow record. The second flow record may include a second quantity of fields, determined based on the second template, that is less than the first quantity of fields. The device may export the second flow record.

Abstract: A network device may receive a packet flow, and may identify an application associated with the packet flow. The network device may determine that packets associated with the application are not to be encrypted using a security protocol. The network device may store a rule that indicates that the packets are not to be encrypted using the security protocol based on determining that the packets are not to be encrypted using the security protocol. The rule may include network layer information or transport layer information associated with the packet flow, and may exclude application layer information associated with the packet flow. The network device may transmit, based on the rule, the packets without using the security protocol to encrypt the packets.