-
Notifications
You must be signed in to change notification settings - Fork 494
profile + blog post for Michael Oviedo #3760
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
base: main
Are you sure you want to change the base?
Conversation
Signed-off-by: Michael Oviedo <[email protected]>
Signed-off-by: Michael Oviedo <[email protected]>
Signed-off-by: Naarcha-AWS <[email protected]>
@Naarcha-AWS @OVI3D0 - What is the status of this blog. Have edits been made? Which OR should we be using here? |
Co-authored-by: Nathan Bower <[email protected]> Signed-off-by: Naarcha-AWS <[email protected]>
Add technical writer edits
Signed-off-by: Michael Oviedo <[email protected]>
@pajuric: The final blog we'll be on this PR. We still have a couple of small tweaks to make before its ready. |
- The pause/unpause events | ||
- The reasons for scaling back | ||
- After the test: | ||
- The maximim number of clients reached |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- The maximim number of clients reached | |
- The maximum number of clients reached |
…k.md Co-authored-by: Naarcha-AWS <[email protected]> Signed-off-by: Michael Oviedo <[email protected]>
…k.md Co-authored-by: Naarcha-AWS <[email protected]> Signed-off-by: Michael Oviedo <[email protected]>
…k.md Co-authored-by: Naarcha-AWS <[email protected]> Signed-off-by: Michael Oviedo <[email protected]>
…k.md Co-authored-by: Naarcha-AWS <[email protected]> Signed-off-by: Michael Oviedo <[email protected]>
…k.md Co-authored-by: Naarcha-AWS <[email protected]> Signed-off-by: Michael Oviedo <[email protected]>
add new flags for redline testing
@pajuric Looks like all the edits have been made, I just would like to delay posting the article until next week as there are a couple small items we would like to iron out related to the feature before posting about it |
_posts/2025-04-24-Redline-Testing-Comes-to-OpenSearch-Benchmark.md
Outdated
Show resolved
Hide resolved
_posts/2025-04-24-Redline-Testing-Comes-to-OpenSearch-Benchmark.md
Outdated
Show resolved
Hide resolved
_posts/2025-04-24-Redline-Testing-Comes-to-OpenSearch-Benchmark.md
Outdated
Show resolved
Hide resolved
## How it works | ||
|
||
The following diagram provides a high-level overview of the actor-based execution flow in OpenSearch Benchmark. It illustrates how benchmark tasks are allocated and executed across multiple worker actors, each of which manages a group of clients responsible for sending requests to a target OpenSearch cluster, using the following components: | ||
|
||
- **BenchmarkActor**: Initiates the benchmarking process. | ||
- **WorkerCoordinatorActor**: Manages worker lifecycle and task distribution using an allocation matrix from the **Allocator**. | ||
- **Workers (Worker1 through WorkerN)**: Executes tasks by managing clients via the **AsyncIoAdapter**. | ||
- **Clients (Client1 through ClientN)**: Uses the `AsyncExecutor` class to perform operations against the target host in parallel. | ||
|
||
{: .img-fluid} | ||
|
||
OpenSearch Benchmark uses the **Actor Model**, which structures concurrent, distributed systems around isolated, message-passing components. | ||
|
||
Each actor performs the following actions: | ||
|
||
- Maintains private, isolated state | ||
- Processes messages sequentially | ||
- Can create other actors | ||
- Communicates asynchronously | ||
|
||
By default, OpenSearch Benchmark spawns `n` worker actors (one per CPU core), distributing clients evenly across them. For example, with 10 workers and 20 clients, each manages 2 clients. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not sure this level of technical detail would be appropriate in a blog post that caters to the community at large, who may not be familiar or interested in internals. Summarizing the gist by indicating that normally client count is static, but this feature permits the count to be increased or decreased dynamically would make this more readable.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let me know what you think of the rewrite I made here!
_posts/2025-04-24-Redline-Testing-Comes-to-OpenSearch-Benchmark.md
Outdated
Show resolved
Hide resolved
_posts/2025-04-24-Redline-Testing-Comes-to-OpenSearch-Benchmark.md
Outdated
Show resolved
Hide resolved
_posts/2025-04-24-Redline-Testing-Comes-to-OpenSearch-Benchmark.md
Outdated
Show resolved
Hide resolved
_posts/2025-04-24-Redline-Testing-Comes-to-OpenSearch-Benchmark.md
Outdated
Show resolved
Hide resolved
_posts/2025-04-24-Redline-Testing-Comes-to-OpenSearch-Benchmark.md
Outdated
Show resolved
Hide resolved
_posts/2025-04-24-Redline-Testing-Comes-to-OpenSearch-Benchmark.md
Outdated
Show resolved
Hide resolved
Signed-off-by: Michael Oviedo <[email protected]>
Signed-off-by: Michael Oviedo <[email protected]>
@OVI3D0 @Naarcha-AWS - Are there still open edits in this blog? Please advise on the status. |
@Naarcha-AWS - Can you update the PR title to Redline testing now available in OpenSearch Benchmark |
Description
Adds a profile page for Michael Oviedo + a blog post for a new redline testing feature in OpenSearch Benchmark (OSB)
Issues Resolved
[List any issues this PR will resolve]
Check List
By submitting this pull request, I confirm that my contribution is made under the terms of the BSD-3-Clause License.