diff options
| author |  Berthold Stoeger <bstoeger@mail.tuwien.ac.at> | 2020-04-13 10:42:42 +0200 |
|---|---|---|
| committer |  Dirk Hohndel <dirk@hohndel.org> | 2020-04-13 08:30:51 -0700 |
| commit | 8b93d67106acaa4f146ee683b837d0b0cf4e31b6 (patch) | |
| tree | a0837ecad8e41965ba822d45a433d538d982973b /core | |
| parent | 9feda560061fca3ade0e22101d810df9f7957a5c (diff) | |
| download | subsurface-8b93d67106acaa4f146ee683b837d0b0cf4e31b6.tar.gz | |
mobile: remove fine-grained notification
When initializing the fulltext-cache and the dive-list, every
100 dives a notification was shown. I had a feeling that this
made startup significantly slower, but that could have been
purely psychological.
Therefore I measured and indeed, removing the fine-grained
notification, it becomes *significantly* faster. For a 3500
dives test log with mobile-on-desktop:
Initialization of the fulltext: 1350 ms -> 730 ms (-46%)
Initialization of the divelistmodel: 689 ms -> 113 ms (-83%)
Let's remove the fine-grained notification. There *is* a visual
indication of work-in-progress anyway.
Signed-off-by: Berthold Stoeger <bstoeger@mail.tuwien.ac.at>
Diffstat (limited to 'core')
| -rw-r--r-- | core/fulltext.cpp | 9 |
1 files changed, 2 insertions, 7 deletions
diff --git a/core/fulltext.cpp b/core/fulltext.cpp index 56b7b2dcc..8bd41e7ff 100644 --- a/core/fulltext.cpp +++ b/core/fulltext.cpp @@ -148,14 +148,9 @@ void FullText::populate() uiNotification(QObject::tr("start processing")); int i; dive *d; - for_each_dive(i, d) { - // this makes sure that every once in a while we allow the - // UI to respond to events - if (i % 100 == 99) - uiNotification(QObject::tr("\r%1 dives processed").arg(i + 1)); + for_each_dive(i, d) registerDive(d); - } - uiNotification(QObject::tr("\r%1 dives processed").arg(dive_table.nr)); + uiNotification(QObject::tr("%1 dives processed").arg(dive_table.nr)); } void FullText::registerDive(struct dive *d) |