-
Notifications
You must be signed in to change notification settings - Fork 49
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
Load testing wip2 #44
base: main
Are you sure you want to change the base?
Load testing wip2 #44
Conversation
cmd/tradeclient/loadtest/loadtest.go
Outdated
responseTime := time.Now() | ||
|
||
localArrival := responseTime | ||
latency := localArrival.Sub(sentTime) |
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.
this latency doesn't seem to be the time from sending the order to the execution report coming back. The flow is asynchronous. After the order is submitted, we need to capture its final response message (i.e. execution report when the order is either filled or cancelled) from the FIX log and check the time spent to fill the order.
mu.Unlock() | ||
}(i) | ||
|
||
time.Sleep(time.Second / time.Duration(cfg.OrdersPerSecond)) |
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.
Could the cadence be dynamic during a day or even 2 days?
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.
it can be done
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.
Are you going to push the change to the public repo?
No description provided.