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

Remove application-id from macrobenchmark config file. #2683

Merged
merged 2 commits into from May 26, 2021
Merged

Conversation

yifanyang
Copy link
Contributor

@yifanyang yifanyang commented May 22, 2021

Also update version for some dependencies.

- update version for some dependencies
- shorten the name of benchmark test class
@google-cla google-cla bot added the cla: yes Override cla label May 22, 2021
@google-oss-bot
Copy link
Contributor

google-oss-bot commented May 22, 2021

Binary Size Report

Affected SDKs

No changes between base commit (b5d06cd) and head commit (0595e450).

Test Logs

Notes

Head commit (0595e450) is created by Prow via merging commits: b5d06cd 7a39540.

@google-oss-bot
Copy link
Contributor

google-oss-bot commented May 22, 2021

Macrobenchmark Report

Affected SDKs

Measurements are for head commit (7a39540). Diffing against base commit (ff8f905) is working in progress.

  • baseline

    NameDeviceMinMaxP50P90P99
    BenchmarkTest.startup[mode=COLD]flame-30-en-portrait117.0 ms174.0 ms142.5 ms161.1 ms173.4 ms
    BenchmarkTest.startup[mode=HOT]flame-30-en-portrait37.0 ms59.0 ms48.0 ms56.0 ms58.4 ms
    BenchmarkTest.startup[mode=WARM]flame-30-en-portrait56.0 ms87.0 ms64.5 ms83.3 ms86.8 ms
  • firebase-common

    NameDeviceMinMaxP50P90P99
    BenchmarkTest.startup[mode=COLD]flame-30-en-portrait133.0 ms169.0 ms149.0 ms168.0 ms168.8 ms
    BenchmarkTest.startup[mode=HOT]flame-30-en-portrait42.0 ms76.0 ms52.0 ms72.3 ms75.8 ms
    BenchmarkTest.startup[mode=WARM]flame-30-en-portrait55.0 ms95.0 ms77.0 ms88.2 ms94.0 ms
  • firebase-config

    NameDeviceMinMaxP50P90P99
    BenchmarkTest.startup[mode=COLD]flame-30-en-portrait131.0 ms171.0 ms144.5 ms161.9 ms170.8 ms
    BenchmarkTest.startup[mode=HOT]flame-30-en-portrait33.0 ms73.0 ms49.5 ms62.0 ms70.9 ms
    BenchmarkTest.startup[mode=WARM]flame-30-en-portrait60.0 ms84.0 ms74.0 ms82.1 ms83.8 ms
  • firebase-crashlytics

    NameDeviceMinMaxP50P90P99
    BenchmarkTest.startup[mode=COLD]flame-30-en-portrait137.0 ms188.0 ms154.0 ms173.5 ms186.1 ms
    BenchmarkTest.startup[mode=HOT]flame-30-en-portrait34.0 ms59.0 ms52.0 ms55.4 ms59.0 ms
    BenchmarkTest.startup[mode=WARM]flame-30-en-portrait58.0 ms92.0 ms72.5 ms90.1 ms91.8 ms
  • firebase-database

    NameDeviceMinMaxP50P90P99
    BenchmarkTest.startup[mode=COLD]flame-30-en-portrait124.0 ms151.0 ms142.5 ms149.2 ms151.0 ms
    BenchmarkTest.startup[mode=HOT]flame-30-en-portrait36.0 ms76.0 ms50.0 ms59.4 ms73.5 ms
    BenchmarkTest.startup[mode=WARM]flame-30-en-portrait52.0 ms87.0 ms69.0 ms77.5 ms86.0 ms
  • firebase-dynamic-links

    NameDeviceMinMaxP50P90P99
    BenchmarkTest.startup[mode=COLD]flame-30-en-portrait123.0 ms164.0 ms149.0 ms154.3 ms162.7 ms
    BenchmarkTest.startup[mode=HOT]flame-30-en-portrait35.0 ms64.0 ms53.0 ms63.0 ms63.8 ms
    BenchmarkTest.startup[mode=WARM]flame-30-en-portrait50.0 ms88.0 ms73.0 ms83.0 ms87.1 ms
  • firebase-firestore

    NameDeviceMinMaxP50P90P99
    BenchmarkTest.startup[mode=COLD]flame-30-en-portrait122.0 ms163.0 ms138.5 ms157.6 ms163.0 ms
    BenchmarkTest.startup[mode=HOT]flame-30-en-portrait30.0 ms69.0 ms49.0 ms63.6 ms69.0 ms
    BenchmarkTest.startup[mode=WARM]flame-30-en-portrait58.0 ms85.0 ms70.5 ms83.1 ms84.8 ms
  • firebase-functions

    NameDeviceMinMaxP50P90P99
    BenchmarkTest.startup[mode=COLD]flame-30-en-portrait138.0 ms171.0 ms151.5 ms164.2 ms170.1 ms
    BenchmarkTest.startup[mode=HOT]flame-30-en-portrait39.0 ms67.0 ms55.5 ms64.3 ms67.0 ms
    BenchmarkTest.startup[mode=WARM]flame-30-en-portrait45.0 ms87.0 ms70.0 ms86.1 ms87.0 ms
  • firebase-inappmessaging-display

    NameDeviceMinMaxP50P90P99
    BenchmarkTest.startup[mode=COLD]flame-30-en-portrait157.0 ms202.0 ms180.0 ms194.5 ms201.4 ms
    BenchmarkTest.startup[mode=HOT]flame-30-en-portrait47.0 ms66.0 ms51.5 ms60.6 ms66.0 ms
    BenchmarkTest.startup[mode=WARM]flame-30-en-portrait56.0 ms89.0 ms77.0 ms87.2 ms89.0 ms
  • firebase-messaging

    NameDeviceMinMaxP50P90P99
    BenchmarkTest.startup[mode=COLD]flame-30-en-portrait137.0 ms243.0 ms153.5 ms173.6 ms230.8 ms
    BenchmarkTest.startup[mode=HOT]flame-30-en-portrait39.0 ms78.0 ms58.0 ms62.6 ms76.1 ms
    BenchmarkTest.startup[mode=WARM]flame-30-en-portrait53.0 ms88.0 ms72.5 ms78.0 ms86.1 ms
  • firebase-perf

    NameDeviceMinMaxP50P90P99
    BenchmarkTest.startup[mode=COLD]flame-30-en-portrait141.0 ms175.0 ms168.0 ms173.1 ms174.8 ms
    BenchmarkTest.startup[mode=HOT]flame-30-en-portrait34.0 ms69.0 ms59.0 ms66.1 ms68.6 ms
    BenchmarkTest.startup[mode=WARM]flame-30-en-portrait56.0 ms103.0 ms73.0 ms85.6 ms102.4 ms
  • firebase-storage

    NameDeviceMinMaxP50P90P99
    BenchmarkTest.startup[mode=COLD]flame-30-en-portrait126.0 ms364.0 ms146.5 ms162.1 ms325.8 ms
    BenchmarkTest.startup[mode=HOT]flame-30-en-portrait39.0 ms77.0 ms52.5 ms65.2 ms75.1 ms
    BenchmarkTest.startup[mode=WARM]flame-30-en-portrait58.0 ms84.0 ms68.0 ms82.1 ms83.8 ms

@yifanyang yifanyang requested review from vkryachko and rlazo May 24, 2021 17:09
@yifanyang
Copy link
Contributor Author

/retest

@yifanyang
Copy link
Contributor Author

/retest

1 similar comment
@yifanyang
Copy link
Contributor Author

/retest

dependencies:
- com.google.firebase:firebase-crashlytics-ktx
plugins:
- com.google.firebase.crashlytics

firebase-database:
name: database
application-id: com.google.firebase.benchmark.database
dependencies:
- com.google.firebase:firebase-database-ktx

firebase-dynamic-links:
name: dynamiclinks
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No immediate action required, but what is the purpose of the name given that we already have the section already named(i.e. firebase-dynamic-links)?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In the beginning, I thought there can be multiple apps built for one SDK, and this name can be used to distinguish those apps, but I suppose that is no longer the case. Right now it's used as part of the dir path for the generated test apps, but it is not necessary to have it in the path. Removing it requires some change, which I'll defer to a followup PR.

Regarding to application id, now that we only need one application id, I'm planning to add it to fireescape-integ-tests so that I can just use preset-google-services in prow jobs. What do you think?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

sgtm

@yifanyang
Copy link
Contributor Author

/retest

@yifanyang
Copy link
Contributor Author

/test check-changed

1 similar comment
@yifanyang
Copy link
Contributor Author

/test check-changed

@yifanyang
Copy link
Contributor Author

/retest

@yifanyang
Copy link
Contributor Author

/test check-changed

5 similar comments
@yifanyang
Copy link
Contributor Author

/test check-changed

@yifanyang
Copy link
Contributor Author

/test check-changed

@yifanyang
Copy link
Contributor Author

/test check-changed

@yifanyang
Copy link
Contributor Author

/test check-changed

@yifanyang
Copy link
Contributor Author

/test check-changed

@yifanyang yifanyang merged commit baec04a into master May 26, 2021
@yifanyang yifanyang deleted the yifany/app-id branch May 26, 2021 01:04
@firebase firebase locked and limited conversation to collaborators Jun 26, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
cla: yes Override cla size/M
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants