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.

Sign up for GitHub

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

Jump to bottom

Benchmark new engine on Android #10

Open
nmittler opened this issue Dec 21, 2016 · 1 comment
Open

Benchmark new engine on Android #10

nmittler opened this issue Dec 21, 2016 · 1 comment
Assignees
@flooey
Labels
needs investigation
Milestone
1.0.1

Comments

@nmittler
Copy link
Contributor

No description provided.

@nmittler nmittler modified the milestone: 1.0.0 Jan 6, 2017
This was referenced Jan 26, 2017
Open
Merged
@nmittler nmittler modified the milestones: 1.0.1, 1.0.0 Feb 27, 2017
@nmittler
Copy link
Contributor Author

@kruton is there any chance we can get some android benchmarks?

@nmittler nmittler assigned flooey and unassigned kruton Jun 30, 2017
flooey pushed a commit to flooey/conscrypt that referenced this issue Aug 3, 2017
Implement Caliper benchmarks for running on Android devices (google#10).
cddedc7 
Netty tcnative doesn't work on ARM, so we split out the Netty-dependent
benchmark portions into benchmark-openjdk and put non-Netty versions
in benchmark-android.

The gradle operations required to execute the benchmarks on devices are ugly,
but they appear to work.  This might get better some time in the future
with improved Caliper support for Android.

This only includes the time-based benchmarks, not the throughput-based ones,
since those will require some more modifications to work in Caliper and these
at least get us started.
flooey pushed a commit to flooey/conscrypt that referenced this issue Aug 4, 2017
Implement Caliper benchmarks for running on Android devices (google#10).
9d26fbe 
Netty tcnative doesn't work on ARM, so we split out the Netty-dependent
benchmark portions into benchmark-openjdk and put non-Netty versions
in benchmark-android.

The gradle operations required to execute the benchmarks on devices are ugly,
but they appear to work.  This might get better some time in the future
with improved Caliper support for Android.

This only includes the time-based benchmarks, not the throughput-based ones,
since those will require some more modifications to work in Caliper and these
at least get us started.
flooey added a commit that referenced this issue Aug 7, 2017
@flooey
Implement Caliper benchmarks for running on Android devices (#10). (#278
e56b72a 
)

Netty tcnative doesn't work on ARM, so we split out the Netty-dependent
benchmark portions into benchmark-openjdk and put non-Netty versions
in benchmark-android.

The gradle operations required to execute the benchmarks on devices are ugly,
but they appear to work.  This might get better some time in the future
with improved Caliper support for Android.

This only includes the time-based benchmarks, not the throughput-based ones,
since those will require some more modifications to work in Caliper and these
at least get us started.
nmittler pushed a commit that referenced this issue Aug 10, 2017
@flooey @nmittler
Implement Caliper benchmarks for running on Android devices (#10). (#278
a8f6555 
)

Netty tcnative doesn't work on ARM, so we split out the Netty-dependent
benchmark portions into benchmark-openjdk and put non-Netty versions
in benchmark-android.

The gradle operations required to execute the benchmarks on devices are ugly,
but they appear to work.  This might get better some time in the future
with improved Caliper support for Android.

This only includes the time-based benchmarks, not the throughput-based ones,
since those will require some more modifications to work in Caliper and these
at least get us started.
@AlbertSnow AlbertSnow mentioned this issue Dec 25, 2019
Open
@ArchanaPrabhu ArchanaPrabhu mentioned this issue Apr 26, 2023
Open
@JasonZhao0608 JasonZhao0608 mentioned this issue Jul 10, 2023
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@flooey flooey

Labels
needs investigation
Projects
None yet
Milestone
1.0.1
Development

No branches or pull requests
3 participants
@kruton @flooey @nmittler