Test: rm ~/.agtl/caches.db
Start agtl
Open Actions Menu (bottom left corner)
Menu is visible instantly
Fetch big amount of caches, 2000 is enough to see effect (then caches.db is about 80MB).
Start agtl
Open Actions Menu (bottom left corner)
Wait three or four seconds
Menu is visible
Pressing actions-menu-button will call _get_fieldnotes_button, which is then calling timeconsuming update_fieldnotes_display, but I don't know any situation where it is needed, because 'fieldnotes-changed' calls it (and it happens also during startup).
Also question could be: why
c = self.conn.execute('SELECT count(*) AS cnt FROM %s WHERE logas != %d' % (self.cache_table, self.ctype.LOG_NO_LOG))
on provider.py:191 takes so much time when cache count is high.
Test: rm ~/.agtl/caches.db Start agtl Open Actions Menu (bottom left corner) Menu is visible instantly
Fetch big amount of caches, 2000 is enough to see effect (then caches.db is about 80MB). Start agtl Open Actions Menu (bottom left corner) Wait three or four seconds Menu is visible
Pressing actions-menu-button will call _get_fieldnotes_button, which is then calling timeconsuming update_fieldnotes_display, but I don't know any situation where it is needed, because 'fieldnotes-changed' calls it (and it happens also during startup).
Also question could be: why
on provider.py:191 takes so much time when cache count is high.