Skip to content
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

Enabling timestamps and copying and pasting many entries is very slow #8975

Open
ThiloteE opened this issue Jul 14, 2022 · 1 comment
Open
Labels
bug Confirmed bugs or reports that are very likely to be bugs type: performance

Comments

@ThiloteE
Copy link
Member

ThiloteE commented Jul 14, 2022

Let me add another performance report: I copied the 10500 entries of my database (the message of having copied the entries came after about 1.2 seconds, fine)). Pasting it into a new empty file took about 9 minutes.
meanwhile, jabref was not usable.

I have now disabled the timestamp and repeated the operation of creating an entirely new database. copying and pasting the >10500 entries was much swifter: 23-26 seconds.

JabRef 5.1--2020-05-04--7bb1e24
Linux 5.6.8-200.fc31.x86_64 amd64
Java 14.0.1

@ThiloteE
Copy link
Member Author

ThiloteE commented Jul 14, 2022

@Christoph @calixtus

Maybe this will be fixed by your refactor of the import format reader and clipboard manager ? :-)

To do:

  • try to reproduce with Refactor of DOI import failure dialog, import format reader and clipboard manager #8839
    Result: Still very slow even with timestamps disabled!
    I copy pasted 10 000 entries (timestamps disabled). I force closed JabRef 29 minutes after start, because the operation seemed to take endless. RAM remained constant. CPU was maxed out:
    grafik

    Edit: Simply copying 500 entries very reliably takes 30 seconds on my laptop. (I did multiple tests). Doing the math, copying 10 000 entries then SHOULD take around 10 minutes, but for some reason it does take a lot longer.

@ThiloteE ThiloteE added type: performance bug Confirmed bugs or reports that are very likely to be bugs labels Jul 14, 2022
@koppor koppor moved this to Normal priority in Prioritization Nov 10, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Confirmed bugs or reports that are very likely to be bugs type: performance
Projects
Status: Normal priority
Development

No branches or pull requests

1 participant