You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
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.
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.
The text was updated successfully, but these errors were encountered: