-
-
Notifications
You must be signed in to change notification settings - Fork 2.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Entry preview: Display delayed for large databases #5735
Comments
Ok, update to the problem: The entry preview will appear, if you wait for 5 to 10 min. This appears to be coupled with the performance problem reported here: The entry preview reappears if you wait 5 to 10 min after starting JabRef. At the same time, the CPU load drops to zero. |
Do you use one of the CSL styles (not the "Preview" )? |
Hmm this is odd. Might be related to #5622 (comment) |
Update 2: Ok, so it seems I can narrow down the problem a little bit. If I use a database, that has been stored using the old release version JabRef 3.8.2 and then open it with the current developer version of JabRef 5.0, the problem appears as described above. Now, if I save this database with the developer version of JabRef 5.0, close it, and then reopen it with the developer version of JabRef 5.0, the entry preview will still not appear immediately. But instead of having to wait 5 to 10 min, it only takes about 30 sec until the actual entry preview (instead of the white background) is shown. |
30 sec for the preview is still too long, and the database size shouldn't matter for this. |
Note, that with the following older version, the entry preview is immediately displayed, irrespective of whether the database still has the old 3.8.2 format or the new 5.0 format: JabRef 5.0-alpha--2019-12-04--5dcb565 |
JabRef 5.0-beta.1--2019-12-14--2e056e6 @bernhard-kleine Cannot confirm. With a database with nearly 20,000 entries, it takes about 30 secs before the entry preview is displayed (using the 5.0 format - with the 3.8.2 format it takes much longer as explained above). Note, that the following older development version of JabRef would display the entry preview immediately: JabRef 5.0-alpha--2019-12-04--5dcb565 |
This should be much faster now in master and will be improved further by the work of @michel-kraemer |
JabRef 5.0-beta.497--2020-02-27--3e0284d @Siedlerchr |
@Siedlerchr : Do you already have a large database (with thousands of entries and thousands of static groups) to test/confirm this issue or do you need me to send one? If the latter is the case, I can try and send one - but since I cannot to make the database available to the public, we would need to find a way around that. |
I could experience some issues with loading (I think it was based your library) ( we have it internally only avaiable for the developers). However, once JabRef has opened the library the preview generation of differnt styles was fast. And also no problems with drag and drop of groups. Tested in Windows 10 |
I have tested it with a library of ~16000 entries, while selecting all entries took some time, displaying the preview was immediate. |
@bernhard-kleine |
10 seconds for opening aside my standard library. Since the large library is not used much the group panel is almost empty. |
This bug may be fixed in the latest development version. Could you please check the build from http://builds.jabref.org/master/. Thanks! Please remember to make a backup of your library before trying-out this version. |
JabRef 5.1--2020-04-20--bc57d22 more than 20,000 items + several thousands of static groups @tobiasdiez : It takes about 90 sec to open the database and see the entry preview. The main table (without the entry preview) is shown after 60 sec, i. e. it still takes about 30 sec to show the entry preview after the main table is already visible. Is that acceptable? Once the the library is fully loaded, the performance is definitely better and the issue mentioned in one of the follow-up comments (#5735 (comment)) has disappeared. |
win7 jabref snapshot 2020-04-18 library 3246 entries: It takes 6 seconds to open jabref and further 12 seconds to load the library (with entry preview). Very similar with the 2020-04-20 snapshot. |
JabRef 5.1--2020-04-23--bbea7df more than 20,000 items + several thousands of static groups Performance has further increased. Well done!
This is a massive improvement compared to previous dev versions. The load up speed is now the same, no matter whether a database in the new v5 format or in the old v3.8.2 format is being used. |
This issue will be closed in 7 days due to inactivity 💤 Please provide the requested information if the problem persists. |
Reaction to github-actions bot: If people are happy with this performance, then you can close the issue. But there is definitely still a delay until the entry preview is shown - JabRef 3.8.2 has no such delay. |
JabRef 5.1--2020-06-02--46fd96b Quick update: If you disable the groups item count as implemented in the current dev version (#6042), the entry preview is shown immediately (or there is a a delay of max. 1 sec) once JabRef has opened. For people with very large databases (>20,000 entries) and several thousands of groups, this change in preferences can definitely improve the performance of JabRef during load up. |
This issue will be closed in 7 days due to inactivity 💤 Please provide the requested information if the problem persists. |
Second reaction to github-actions bot: If people are happy with this performance, then you can close the issue. But there is definitely still a noticeable delay until the entry preview is shown, if the group item count is displayed. If it isn't, the delay is max. 1 sec, which I reckon people would be fine with. |
For 3264 entries about 7 sec, for 16620 entries without heavy grouping no delay. |
This issue will be closed in 7 days due to inactivity 💤 Please provide the requested information if the problem persists. |
JabRef 5.0-alpha--2019-12-11--c3b7ee7
Windows 10 10.0 amd64
Java 13.0.1
In the current dev version of JabRef the entry preview is no longer displayed - it is just a white field.
The text was updated successfully, but these errors were encountered: