switch map to unordered_map
Generally, unordered_maps should be preferred over map because they have
faster access times (O(1)) and tend to allocate less dynamic memory. We
do not rely on ordered iteration in any current use of maps, so it is
safe to do a full replace.
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: Ieaa28ac7f70f9913d13d25142fea9861d49bb23f
diff --git a/manager/manager.hpp b/manager/manager.hpp
index 20f8aaa..88875d1 100644
--- a/manager/manager.hpp
+++ b/manager/manager.hpp
@@ -3,9 +3,9 @@
#include "ledlayout.hpp"
#include "utils.hpp"
-#include <map>
#include <set>
#include <string>
+#include <unordered_map>
namespace phosphor
{
@@ -69,7 +69,7 @@
}
using group = std::set<phosphor::led::Layout::LedAction>;
- using LedLayout = std::map<std::string, group>;
+ using LedLayout = std::unordered_map<std::string, group>;
/** @brief static global map constructed at compile time */
const LedLayout& ledMap;
@@ -131,7 +131,7 @@
sdbusplus::bus::bus& bus;
/** Map of physical LED path to service name */
- std::map<std::string, std::string> phyLeds{};
+ std::unordered_map<std::string, std::string> phyLeds{};
/** DBusHandler class handles the D-Bus operations */
DBusHandler dBusHandler;