![]() ![]() My OS is Linux - Fedora 34 (kernel 5.16.8), Laptop: RAM 32GB, 12 cores Intel i7ĭBeaver: Version 21.12130652 which is newer than the last version mentioned in this thread with an update. I have tried to bump the memory for DBeaver to 4GB, but didn't help, so JVM memory doesn't seem to be an issue. I don't expect vim like performance, but I pasted the same text (and more, 20 lines of such inserts) and my IntelliJ didn't even notice, everything fast and smooth even with the VIM plugin enabled. a generated SQL to insert data from an existing table), I only have a single INSERT that is 120k character long and it completely locks up the editor for seconds when moving the cursor around, it freezes on keystrokes, runs one CPU at 100% with fans spinning high to keep my laptop cool - with one word unusable. I have noticed that if I paste SQL into the editor with long lines (e.g. Hi, I'm not sure if this is the same issue. ![]() Probably I need to test some particular data types. Could you make another test - hide columns with "expensive" data types (right click on column header->Hide column) and see which ones render slower than others. I see that you have datetime, uuid and jsonb columns. Potentially icons rendering (for booleans or FKs), complex texts (jsonb), arrays, structures - may consume much CPU.Īlthough I still can't reproduce it on my Windows machine (even on 4k monitor). ![]() Some columns rendering may get much more CPU than another. It is not even activated before you switch to ERD It is definitely related to a number of visible cells. I think that ERD has nothing to do to it. Perhaps 10-15% of render time - if you have a lot of numeric/timestamp values. On Windows it will save about 10% of render time, on MacOS it may be much more, need to test it disabling right-justification will improve performance (we need to pre-render cell values to do it). I've added a couple of small improvements. Could also be because of high pixel density. No one wants to click on a cell while they are scrolling really fast anyway.Īlso if you click you stop scrolling so that solves that problem. That would allow you to scroll trough a huge table without the refresh rate crashing. If so, there should be a delay on rendering those inputs until you stop scrolling. Truly hope you can find the cause easily! It must be something like, rendering inputs while scrolling. (I have to scroll trough lots of tall and wide tables and look for inconsistencies. Making it impossible to use it in my workflow. And if I look at a large table trough a small window all is fine, but if the window size increases, the refresh rate of the view gets worse. Small sidebar panels and small grid views are fast and snappy. I think it's a bug that could be reproduced on any mac. I have the same issue and so does my colleague. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |