It’s taking anywhere from ten seconds to thirty seconds to load the dropdowns for columns. This is even on brand new databases with no rows and only 5 or so columns. I also posted this a while back, but I got no response:
Sorry, I didn’t see that old thread. Are you bumping exactly the same issue or is this slightly different? If it’s the same issue, I just want to close that old thread and link here.
And does this happen every time the page loads, or just the first time after the DB is changed?
I’ll take a look internally, I’m guessing this is just a poorly optimized query path.
The same issue, just has gotten worse (at least I think it has) recently. Similar blocks get the data much faster, it’s just get rows by values that’s slow.
Just when the DB is changed
That’s strange, I’d expect slow query performance to happen every time the data needs to be looked up. This might be some kind of caching issue then.
I’ll take a look later and see if I can reproduce this.
I can only partially reproduce this. The client long-polls for this data, so after changing DB it takes a few seconds to update, but refreshing pulls the data instantly.
I can look into either tightening up the long-poll loop or having it trigger a fetch directly, but first I want to confirm that I’m seeing the same issue and not some other performance problem (since the issue persisting even if you refresh would imply a much bigger/stateful problem).
Can you show a video or some kind of repro of changing the db then refreshing and still needing to wait, so I can see the behavior? If you can’t repro let me know too and I’ll just work on getting the long-polling to be a bit faster.
Does seem to work for refreshing now! It was a while back that I encountered the refresh not seeming to work, and I never retried it.