log: use smaller buffer for ConcreteEntry

This brings down the static size of the memory used by the logging infrastructure:

    If we used 1024, we'd have 1088*10000 = 10880000 = 10MB in use by the ring
    buffer and 2*1088*100 = 2*108800 = 2*106KB for the m_new and m_flush
    vectors.

In my testing, 1024 covers most log entries.

Note, I've kept 4096 for the StackStringStream via MutableEntry as these are
already allocated on the heap and cached in a thread local vector. Generally
there should only be about a dozen of these allocated so it's worth keeping a
larger buffer.

Signed-off-by: Patrick Donnelly <pdonnell@redhat.com>
This commit is contained in:
Patrick Donnelly 2018-09-06 08:52:25 -07:00
parent b86994e3f9
commit 9c10509092
No known key found for this signature in database
GPG Key ID: 3A2A7E25BEA8AADB

View File

@ -107,7 +107,7 @@ public:
}
private:
boost::container::small_vector<char, 4096> str;
boost::container::small_vector<char, 1024> str;
};
}