You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Useless time consuming internal SQL-commands at start-up and at browsing data?? #503
I observed, that just opening a big sqlite-file tooks lots of time. At the SQL_Log panel I could see that SQLitebrowser first queries the sql_temp_master table, which is ok for me, but then also automatically queries the first table inside the db file. Just to show me nothing else more than the entry panel with the file structure. I think the last query is pretty useless, cause switching to data panel issues the query for the first table again!
Second:
If then I will have a look at the data and right-click on the table of choice and clicking Browse Table then SQLitebrowser issues 2 queries: 1st) for the last table (looked at or automatically queried by program start) and 2nd) for the actual table I want to look at. Again I think the first query is pretty useless!?
changed the title [-]Useless timeconsuming internal SQL-commands??[/-][+]Useless time consuming internal SQL-commands at start-up and at browsing data??[/+]on Jan 22, 2016
Hmmmm, yeah, you're probably right. It's kind of a semi-legacy code base, and we haven't really optimised things for working with large databases. It would be useful for someone to join the team who'd be interested in doing that.
Would you happen to know anyone suitable and who might have the time/interest? 😀
we were on this before, unfortunately not. I can only offer my interest in beta testing/usability testing/reporting issues I stumble upon. But I’m not a programmer or know of anyone here.
Both issues should be fixed in the next nightly build. Let's have a thorough test here because this required changing some of the more central parts of the UI code 😄
I’m on Windows 7 SP1, tests with actual nightly build from 29.01.2016:
Issue 1) SQLiteBrowser now loads lightning fast – good!
Issue 2) just clicking on the tab Browse Data results in incremental loadings of data in 50000 steps, which took looooooooong time - and finally crashed on a big data file, on small data file there is no crash; but the incremental loadings are not the behavior as before and pretty useless for a first glance at the file.
I answer per mail and put screenshots into it – dunno if it makes it to the forum …
@zwrmueller Any interesting in testing a build with (significant) performance enhancements for the Browse Data tab? If so, we've just chucked them up on the nightlies server:
@zwrmueller The improvement that we mentioned is already available in our nightly builds and will be available in our next release. Would you mind confirming that the issue is fixed for you?
One thing I noticed (still in latest nightly) is that sometimes, the browse data tab can be interrupted, but most of the time if the first query is a slow one it just hangs the UI.
Activity
[-]Useless timeconsuming internal SQL-commands??[/-][+]Useless time consuming internal SQL-commands at start-up and at browsing data??[/+]justinclift commentedon Jan 22, 2016
Hmmmm, yeah, you're probably right. It's kind of a semi-legacy code base, and we haven't really optimised things for working with large databases. It would be useful for someone to join the team who'd be interested in doing that.
Would you happen to know anyone suitable and who might have the time/interest? 😀
zwrmueller commentedon Jan 22, 2016
Hello Justin,
we were on this before, unfortunately not. I can only offer my interest in beta testing/usability testing/reporting issues I stumble upon. But I’m not a programmer or know of anyone here.
I’m sorry
Ralf
justinclift commentedon Jan 22, 2016
No worries at all. I ask widely because sometimes it works out well. 😁
Reduce number of unneededly executed SQL commands
MKleusberg commentedon Jan 27, 2016
Both issues should be fixed in the next nightly build. Let's have a thorough test here because this required changing some of the more central parts of the UI code 😄
justinclift commentedon Jan 28, 2016
@zwrmueller Do you have time to test the next nightly build (tomorrow), and let us know if it's working better for you now? 😄
zwrmueller commentedon Jan 28, 2016
Sure, that’s the least that I can do.
Regards
Ralf
zwrmueller commentedon Jan 29, 2016
Hi, here is my testing:
I’m on Windows 7 SP1, tests with actual nightly build from 29.01.2016:
Issue 1) SQLiteBrowser now loads lightning fast – good!
Issue 2) just clicking on the tab Browse Data results in incremental loadings of data in 50000 steps, which took looooooooong time - and finally crashed on a big data file, on small data file there is no crash; but the incremental loadings are not the behavior as before and pretty useless for a first glance at the file.
I answer per mail and put screenshots into it – dunno if it makes it to the forum …
Regards
Ralf
justinclift commentedon Jan 30, 2016
Thanks Ralf. And yeah, email attachments don't get added to issues. They need to be added using the web interface. Would you be ok to do that? 😄
zwrmueller commentedon Jan 30, 2016
new startup - OK!
was old startup - with immediate query - bad
new BrowseData - with incremental data queries - bad
new BrowseData - with crash on big data file
old BrowseData - with double time useless SQL query - not optimal
Regards
Ralf
justinclift commentedon Jan 31, 2016
Thanks Ralf. 😄
justinclift commentedon May 26, 2018
@zwrmueller Any interesting in testing a build with (significant) performance enhancements for the Browse Data tab? If so, we've just chucked them up on the nightlies server:
In my testing of a ~600MB database file, the lag time when using the Browse Data tab is now around 1 second. That's a lot better than it used to be. 😄
mgrojo commentedon Oct 5, 2018
@zwrmueller The improvement that we mentioned is already available in our nightly builds and will be available in our next release. Would you mind confirming that the issue is fixed for you?
chrisjlocke commentedon Jan 8, 2019
Hi @zwrmueller - just checking if you're still interested in checking one of our nightly builds?
wmertens commentedon Jan 15, 2019
One thing I noticed (still in latest nightly) is that sometimes, the browse data tab can be interrupted, but most of the time if the first query is a slow one it just hangs the UI.