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

JabRef performance issues with large bib file #1094

Closed
simonharrer opened this Issue Apr 4, 2016 · 9 comments

Comments

Projects
None yet
5 participants
@simonharrer
Contributor

simonharrer commented Apr 4, 2016

JabRef version 3.x on Windows 10

Steps to reproduce:

  1. Create BibTeX file with 100000 entries. (automatically generated using a ruby script)
  2. Open with JabRef
  3. Wait for nothing to happen for a few minutes
  4. JabRef opens but is very unresponsive.

test.zip

@tobiasdiez

This comment has been minimized.

Show comment
Hide comment
@tobiasdiez

tobiasdiez Apr 4, 2016

Member

Well, the loading time was acceptable for me (< 1 min) but JabRef uses 2 GB of memory :). Will have a look at it.

Member

tobiasdiez commented Apr 4, 2016

Well, the loading time was acceptable for me (< 1 min) but JabRef uses 2 GB of memory :). Will have a look at it.

@tobiasdiez tobiasdiez self-assigned this Apr 4, 2016

@stefan-kolb

This comment has been minimized.

Show comment
Hide comment
@stefan-kolb

stefan-kolb Apr 4, 2016

Member

There are several things that can cause this problems:

  • Autocompletion performance is not optimized
Member

stefan-kolb commented Apr 4, 2016

There are several things that can cause this problems:

  • Autocompletion performance is not optimized
@simonharrer

This comment has been minimized.

Show comment
Hide comment
@simonharrer

simonharrer Apr 4, 2016

Contributor

You could try to profile it using jvisualvm which is shipped with Java. The script which generates the bib file is available since 1edd7d3

Contributor

simonharrer commented Apr 4, 2016

You could try to profile it using jvisualvm which is shipped with Java. The script which generates the bib file is available since 1edd7d3

@Siedlerchr

This comment has been minimized.

Show comment
Hide comment
@Siedlerchr
Contributor

Siedlerchr commented Apr 4, 2016

@tobiasdiez

This comment has been minimized.

Show comment
Hide comment
@tobiasdiez

tobiasdiez Apr 4, 2016

Member

I actually plan to write a few benchmarks using JMH. So we have a reliable way to later gauge if some changes improve the performance or not.

Member

tobiasdiez commented Apr 4, 2016

I actually plan to write a few benchmarks using JMH. So we have a reliable way to later gauge if some changes improve the performance or not.

@simonharrer simonharrer referenced this issue Apr 4, 2016

Merged

Fast search #1100

3 of 3 tasks complete
@stefan-kolb

This comment has been minimized.

Show comment
Hide comment
@stefan-kolb

stefan-kolb Apr 7, 2016

Member

For me, save as takes ages when selecting a crowded folder. Dunno if this is somehow related to JabRef or only Java in general.

Member

stefan-kolb commented Apr 7, 2016

For me, save as takes ages when selecting a crowded folder. Dunno if this is somehow related to JabRef or only Java in general.

@koppor

This comment has been minimized.

Show comment
Hide comment
@koppor

koppor Apr 26, 2016

Member

The first benchmarks have been done in #1103.

Member

koppor commented Apr 26, 2016

The first benchmarks have been done in #1103.

@stefan-kolb

This comment has been minimized.

Show comment
Hide comment
@stefan-kolb

stefan-kolb May 9, 2016

Member

Close this for now? We got significantly better on the major points didn't we?

Member

stefan-kolb commented May 9, 2016

Close this for now? We got significantly better on the major points didn't we?

@simonharrer

This comment has been minimized.

Show comment
Hide comment
@simonharrer

simonharrer May 9, 2016

Contributor

There is still room for improvement. But as far as I know it is good enough at the moment.

Contributor

simonharrer commented May 9, 2016

There is still room for improvement. But as far as I know it is good enough at the moment.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment