Skip to content

Conversation

@shreyas-gopalakrishna
Copy link
Member

@shreyas-gopalakrishna shreyas-gopalakrishna commented Jan 4, 2023

Worker code path warmup

Use the HostWarmupMiddleware to send the WorkerWarmupRequest to warm up the worker code path before specialization.

PR for protobuf changes: Azure/azure-functions-language-worker-protobuf#84

Pull request checklist

  • My changes do not require documentation changes
    • Otherwise: Documentation issue linked to PR
  • My changes should not be added to the release notes for the next release
    • Otherwise: I've added my notes to release_notes.md
  • My changes do not need to be backported to a previous version
    • Otherwise: Backport tracked by issue/PR #issue_or_pr
  • My changes do not require diagnostic events changes
    • Otherwise: I have added/updated all related diagnostic events and their documentation (Documentation issue linked to PR)
  • I have added all required tests (Unit tests, E2E tests)

@safihamid safihamid requested a review from fabiocav January 10, 2023 22:14
Copy link
Member

Choose a reason for hiding this comment

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

If worker is not supporting this capability, don't we need to set the result (to false)? Because ProcessWorkerWarmupResponse will not execute in that case. Correct? I know we await this method and I am wondering that will handle the tasks status "WaitingForActivation" (The default status) in this case.

Copy link
Contributor

@safihamid safihamid left a comment

Choose a reason for hiding this comment

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

:shipit:

@shreyas-gopalakrishna shreyas-gopalakrishna merged commit 3bea4c7 into dev Feb 2, 2023
@shreyas-gopalakrishna shreyas-gopalakrishna deleted the shreyasg/java-warmup branch February 2, 2023 17:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants