Skip to content

Crank SignalR Testing topology in Azure #37909

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

Open
8 tasks
bradygaster opened this issue Oct 28, 2021 · 1 comment
Open
8 tasks

Crank SignalR Testing topology in Azure #37909

bradygaster opened this issue Oct 28, 2021 · 1 comment
Assignees
Labels
area-signalr Includes: SignalR clients and servers Priority:1 Work that is critical for the release, but we could probably ship without
Milestone

Comments

@bradygaster
Copy link
Member

bradygaster commented Oct 28, 2021

We want to create a testing environment for perf testing SignalR in Azure using Crank. Some details of this topology:

  • VM running the Crank server
  • 5 ACI's, each running a containerized app that connects to the Crank-hosted Hub and starts sending messages

Thing to be done (team, please augment, let's write it down):

  • @bradygaster to write a bicep template to create the VM and other Azure resources
  • @bradygaster to send a PR for the bicep file once it's creating resources properly
  • tbd to provide a sample server and client project to do the work
  • tbd (probably @bradygaster) to write script that installs/configures/runs the Crank server on the VM
  • tbd (probably @bradygaster) to write script that builds the docker images and publishes them to ACR and fires up the ACI instances so they can turn the crank
  • tbd to provide other items @bradygaster forgot or omitted here
@bradygaster bradygaster added the area-signalr Includes: SignalR clients and servers label Oct 28, 2021
@bradygaster bradygaster self-assigned this Oct 28, 2021
@rafikiassumani-msft rafikiassumani-msft added this to the .NET 7 Planning milestone Oct 28, 2021
@rafikiassumani-msft rafikiassumani-msft added Cost:M Priority:1 Work that is critical for the release, but we could probably ship without labels Jan 13, 2022
@ghost
Copy link

ghost commented Oct 11, 2022

Thanks for contacting us.

We're moving this issue to the .NET 8 Planning milestone for future evaluation / consideration. We would like to keep this around to collect more feedback, which can help us with prioritizing this work. We will re-evaluate this issue, during our next planning meeting(s).
If we later determine, that the issue has no community involvement, or it's very rare and low-impact issue, we will close it - so that the team can focus on more important and high impact issues.
To learn more about what to expect next and how this issue will be handled you can read more about our triage process here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-signalr Includes: SignalR clients and servers Priority:1 Work that is critical for the release, but we could probably ship without
Projects
None yet
Development

No branches or pull requests

4 participants