Skip to content

Separate basic functionality from Track 2 specific dependencies in perf / stress framework #45166

Open
@alzimmermsft

Description

@alzimmermsft

Right now, perf-test-core, the basic layer for all performance and stress testing, consumes Track 2 dependencies such as azure-core-http-netty. This forces libraries that aren't on the same track of code, such as the previous com.microsoft.azure packages and the io.clientcore packages, to bring in dependencies that they won't use and possibly conflict with the dependencies in that track.

We should look at either simplifying perf-test-core to the most basic infrastructure needed for performance and stress testing or create a layer underneath perf-test-core that is and have perf-test-core build on top of that new library.

Metadata

Metadata

Assignees

No one assigned

    Labels

    StressThis issue is related to stress testing, part of our reliability pillar.commoncommon module used by all azure SDKs (e.g. client, Mgmt)pillar-performanceThe issue is related to performance, one of our core engineering pillars.

    Type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions