Reduce the maximum database size to 200MB until we have fixed the lmdb

issues.

https://phabricator.kde.org/T8723

With 200MB we can both deal with the 200MB files on disk, and we could
even load all of them (the 5 databases the resource uses), into memory.
Once the open problems are resolved we should be able to bump it back to
at least 20GB.

1 files changed, 1 insertions, 1 deletions

diff --git a/common/storage_lmdb.cpp b/common/storage_lmdb.cpp
index 201e1a0..fe3b303 100644
--- a/common/storage_lmdb.cpp
+++ b/common/storage_lmdb.cpp
@@ -929,7 +929,7 @@ static size_t mapsize()
     }
 #ifdef Q_OS_WIN
     //Windows home 10 has a virtual address space limit of 128GB(https://msdn.microsoft.com/en-us/library/windows/desktop/aa366778(v=vs.85).aspx#physical_memory_limits_windows_10). I seems like the 128GB need to accomodate all databases we open in the process.
-    return (size_t)1048576 * (size_t)10000; // 1MB * 10'000
+    return (size_t)1048576 * (size_t)200; // 1MB * 200
 #else
     //This is the maximum size of the db (but will not be used directly), so we make it large enough that we hopefully never run into the limit.
     return (size_t)1048576 * (size_t)100000; // 1MB * 100'000