-
Notifications
You must be signed in to change notification settings - Fork 119
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
Confirm shards are running in parallel #623
Comments
This will be solved soon by server side sharding. FTL implemented this and I've done work to prototype what it'd look like in Flank. Unfortunately TestArmada has reduced permissions of non-Walmart employees. I expect on Jan 2 we'll get approval from Walmart to transfer Flank into the Flank GitHub org and then feature development will resume. My guess is that FTL is queueing some of your executions which don't show up in the execution time but will result in clock wall time. |
sweet! I saw that https://issuetracker.google.com/issues/115928363#comment4 Looking forward to it. |
Hey, server side sharding is implemented on master. We also have a shiny new Flank org on GitHub. 🙂 |
I'm seeing this as well. In which version is this fixed? |
this should be fixed in the snapshot release |
We've been running with this for a month or more. Very nice work y'all. Thanks a million for the hard work! |
We are using the Flank |
I initially was concerned about whether shards were run parallel or not, but didn't have good logs to confirm, So I raised #577
Now that we have good logs (thanks BTW) I still don't think our shards are run in parallel (despite what I said here )
Here are our most recent logs: https://gist.github.com/tir38/ee2bf14148e7d7c14aa2be48c59a2de1
We run 5 devices and 5 shards
We are seeing each shard take ~4-5 minutes
But the total task time is closer to 20 minutes:
I know @bootstraponline said before that "running multiple matrices to enable parallel execution isn't ideal" Is it possible that FTL is delaying each shard?
The text was updated successfully, but these errors were encountered: