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

[WIP] Performance tests for Akka, Remote, Cluster in .NET Core #2768

Closed
wants to merge 4 commits into from
Closed

[WIP] Performance tests for Akka, Remote, Cluster in .NET Core #2768

wants to merge 4 commits into from

Conversation

heynickc
Copy link
Contributor

Enables performance tests for .NET Core versions of Akka.Tests.Performance, Akka.Remote.Tests.Performance, and Akka.Tests.Cluster.Performance. Limits the installation of NBench.Runner.exe to only runs of target: NBench since NBench.Runner v1.0.4 includes .NET Core standalone executables which include the .NET Core 1.1 runtime.

@heynickc heynickc changed the title Performance tests for Akka, Remote, Cluster Performance tests for Akka, Remote, Cluster in .NET Core Jun 16, 2017
@@ -61,7 +61,8 @@ Target "Build" (fun _ ->
(fun p ->
{ p with
Project = project
Configuration = configuration })
Configuration = configuration
AdditionalArgs = ["--no-incremental"]}) // i.e. "Rebuild"
Copy link
Contributor Author

Choose a reason for hiding this comment

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

Additional change - we should be calling "Rebuild" to be consistent with previous build script.

@heynickc
Copy link
Contributor Author

If this PR is merged, we can take out the BuildRelease step from "Windows Performance Tests" in CI since this only selectively builds the necessary projects to run PerfTests


// .NET Core ---------------------------------------
// Publish netcoreapp1.1 performance test assemblies
let performanceTestProjects = !! "./**/*.Tests.Performance.csproj"
Copy link
Contributor

@alexvaluyskiy alexvaluyskiy Jun 17, 2017

Choose a reason for hiding this comment

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

Each test run for performance tests takes 45 minutes right now, we can't just double it. We have to run them separately

* v1.3:
  HandleMsg used instead of AssociationHandle (#2753)
  Limits the number of concurrent Persistent actors during recovery (#2655)
  Added tutorials to the new documentation (#2727)
  put mntr specs in correct output folder and ignore launchSettings.json (#2759)
@alexvaluyskiy alexvaluyskiy mentioned this pull request Jul 4, 2017
18 tasks
@heynickc heynickc changed the title Performance tests for Akka, Remote, Cluster in .NET Core [WIP] Performance tests for Akka, Remote, Cluster in .NET Core Jul 6, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants