Re: [PATCH 04/23] t/helper/fsmonitor-client: create stress test
- From
- Jeff Hostetler <git@jeffhostetler.com>
- Date
- Mar 1, 2022, 19:37 UTC
- Message-ID
- <0baa2939-bf3c-b08b-2cfc-5a96be760b1c@jeffhostetler.com>
- In-Reply-To
- <ab3d1fc7-e63a-dff4-f373-a6ac32b8294a@github.com>
On 2/24/22 9:58 AM, Derrick Stolee wrote:
Show 14 quoted lines
> On 2/15/2022 10:59 AM, Jeff Hostetler via GitGitGadget wrote: >> From: Jeff Hostetler <jeffhost@microsoft.com> >> >> Create a stress test to hammer on the fsmonitor daemon. >> Create a client-side thread pool of n threads and have >> each of them make m requests as fast as they can. >> >> NEEDSWORK: This is just the client-side thread pool and >> is useful for interactive testing and experimentation. >> We need to add a script test to drive this. > > I haven't gotten far enough in the series to know if you > _do_ use this in a test eventually. If so, this NEEDSWORK > could be replaced with a mention of a future change.
Right. I mainly use this test helper to hammer on the daemon during interactive tests. I don't have a script to actually use. I'm currently not sure what that would look like given our test script framework.
Show 7 quoted lines
> >> + /* >> + * TODO Decide if/when to return an error or call die(). >> + */ >> + return 0; > > This TODO could be cleaned up.
good catch. thanks!
Jeff