-
Notifications
You must be signed in to change notification settings - Fork 858
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
Optimize performance in test262 #1671
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
NativeJavaListTest > length FAILED RegexpTest > unsupportedFlagCtor FAILED |
bc214e4
to
dafed6d
Compare
Fixed the condition in the "filter"method. Now ShellTimerTest fails. Waiting for #1672, then I'll do a rebase |
Improves the startup time from about 3 sec to < 1 sec
dafed6d
to
3b41680
Compare
/** Returns the current filename in the java stack. */ | ||
@SuppressWarnings("AndroidJdkLibsChecker") | ||
// Android uses interpreter, so we should not get here. | ||
static String getSourcePositionFromJavaStack(int[] linep) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Rebase is done. Maybe someone can confirm, that android always uses interpreter, so we should not get here ;)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@rPraml thanks for that, faster tests are always a good thing |
This PR targets two issues I found with a profiler, while running the 262 test suite:
addTestFiles
has a nested loop with a complexity of O(n^2). I've replaced this with a hashmap, that improves startup time from ~3 sec down to <1 sec