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

Slowdown when enabling invokedynamic for YAML + ActiveRecord example #1023

Closed
donv opened this issue Sep 18, 2013 · 4 comments
Closed

Slowdown when enabling invokedynamic for YAML + ActiveRecord example #1023

donv opened this issue Sep 18, 2013 · 4 comments

Comments

@donv
Copy link
Member

donv commented Sep 18, 2013

Given the example for issue #1005 for equal settings just enabling invokedynamic the performance is halved (run time is doubled).

The core of the example is reading and parsing a YAML file and storing records in ActiveRecord using DerbyDB (JavaDB).

Performance should be equal or better with invokedynamic enabled.

@headius
Copy link
Member

headius commented Sep 19, 2013

I spent some time investigating, and I can reproduce your results.

For non-indy, the load takes about 1m. With indy, it takes 2m. If I set +TieredCompilation, those reduce to 51s/89s...a better ratio but still close to 2x slower.

I've posted emails to the MLVM list about my findings. I have been using Java Mission Control to investigate and have found some interesting things.

Would it be ok if I let the JVM guys have at your app? Is there a way we can make it run longer, perhaps by wiping DB and starting over?

@donv
Copy link
Member Author

donv commented Sep 19, 2013

Yes, I'd be happy have the JVM guys look at our app.

The issue_1005.sh script already wipes the db on each run.

A larger message file will make the app run longer. We can also trigger loading the same file multiple times. Our full app takes up to 10 minutes to process a full update, but that involves many more models.

I could pretty easily generate a huge message file for you. It is pretty simple.

@enebo
Copy link
Member

enebo commented Feb 17, 2017

@headius @donv this is 3+ years old and indy and our runtimes have changed a lot. @donv is there a way you can check to see if this is still an issue?

@donv
Copy link
Member Author

donv commented Mar 30, 2017

Hi!

Sorry for the late reply. Still 1000 messages behind on the JRuby mailing list 😄 .

Since this issue is so old, and the world has changed so much, I will close this issue.

I will open a new issue if I try InDy in the future. All our production systems run without InDy.

@donv donv closed this as completed Mar 30, 2017
@enebo enebo added this to the Invalid or Duplicate milestone May 11, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants