diff options
author | shess <shess@chromium.org> | 2015-08-25 10:39:51 -0700 |
---|---|---|
committer | Commit bot <commit-bot@chromium.org> | 2015-08-25 17:40:44 +0000 |
commit | 2d48e948d46a3c288e7147867a5978aa647b2344 (patch) | |
tree | 28c833e24186a5568ca0788309c52f8e87d51352 /sql/connection.cc | |
parent | ed8af5cd9c7fe6d79a759d8e79e4a042c7b3d524 (diff) | |
download | chromium_src-2d48e948d46a3c288e7147867a5978aa647b2344.zip chromium_src-2d48e948d46a3c288e7147867a5978aa647b2344.tar.gz chromium_src-2d48e948d46a3c288e7147867a5978aa647b2344.tar.bz2 |
[sql] Record SQLite memory usage after a week.
Previously landed 10-minute, 1-hour, and 1-day histograms. Based on
those I expect 1-week to get around 20% worse.
BUG=489784
Review URL: https://codereview.chromium.org/1316493006
Cr-Commit-Position: refs/heads/master@{#345366}
Diffstat (limited to 'sql/connection.cc')
-rw-r--r-- | sql/connection.cc | 8 |
1 files changed, 8 insertions, 0 deletions
diff --git a/sql/connection.cc b/sql/connection.cc index 2fcc9da..3f37b90 100644 --- a/sql/connection.cc +++ b/sql/connection.cc @@ -128,6 +128,11 @@ void RecordSqliteMemoryDay() { UMA_HISTOGRAM_COUNTS("Sqlite.MemoryKB.OneDay", used / 1024); } +void RecordSqliteMemoryWeek() { + const int64 used = sqlite3_memory_used(); + UMA_HISTOGRAM_COUNTS("Sqlite.MemoryKB.OneWeek", used / 1024); +} + // SQLite automatically calls sqlite3_initialize() lazily, but // sqlite3_initialize() uses double-checked locking and thus can have // data races. @@ -155,6 +160,9 @@ void InitializeSqlite() { base::MessageLoop::current()->PostDelayedTask( FROM_HERE, base::Bind(&RecordSqliteMemoryDay), base::TimeDelta::FromDays(1)); + base::MessageLoop::current()->PostDelayedTask( + FROM_HERE, base::Bind(&RecordSqliteMemoryWeek), + base::TimeDelta::FromDays(7)); } first_call = false; |