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

No stress tests different pools in this repository #40

Open
3 tasks
anfelbar opened this issue Nov 4, 2022 · 1 comment
Open
3 tasks

No stress tests different pools in this repository #40

anfelbar opened this issue Nov 4, 2022 · 1 comment

Comments

@anfelbar
Copy link
Collaborator

anfelbar commented Nov 4, 2022

Description

Currently, this repository has one way to generate an intense load to a cluster by means of bazel genrules in directory named genrules. It uses an upper bound to generate txt files, and copy pdf and tar.gz files, allowing for generating thousandths of targets. However, no other example provides this capability making it difficult to generate an intense load in the different pools a customer or our own clusters may have. It is desirable then to implement examples that generate intense loads on different pools, mainly typescript and macos pools (using swift?). It should also be possible to create specific heavy loads that target gpu based instances, like those ones the cluster bornite has, by using matrix operations or things of the sort.

Should have

  • Implement cpu intense program for specific languages to be built on a specific pool.
    1. linux pool: languages like java, go and python
    2. macos pool: languages like scala, swift and csharp
    3. ts pool: typescript
  • Allow to customize how intense the load will be by means of parameters

Double-check

  • linux pool examples
  • macos examples
  • ts example
@anfelbar
Copy link
Collaborator Author

anfelbar commented Nov 4, 2022

WDYT @lfpino?

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

No branches or pull requests

1 participant