TimelyDataflow / TimelyDataflow/timely-dataflow
BigData series
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 3.6k
- Forks
- 293
- Avg merge
- 14h 46m
- Merged PRs (30d)
- 4
Description
Hey,
I wanted to let you know there is an early version of the part 5 of my big data series here:
https://github.com/kali/kali.github.io/blob/master/_drafts/Embrace_the_glow_cloud.md
The results graphs are here:
https://github.com/kali/kali.github.io/blob/master/assets/2016-02-11-m3xl.png
https://github.com/kali/kali.github.io/blob/master/assets/2016-02-11-m32xl.png
https://github.com/kali/kali.github.io/blob/master/assets/2016-02-11-c38xl.png
I am a bit puzzled by the fact the huge c3.8xl instances are performing so badly in network configuration (probing show network is fairly good, 6 or 7 several GB/s whether or not there are started in the same "placement group").
I will also investigate if my use of ansible as a way to start the processes is not offsetting their start time enough to forbid getting under the 7 or 8 second limit. I'll try to find some trick to start all instances more simultaneously.
Anyway. If you want to shed some wisdom, feel free to.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Read _drafts/Embrace_the_glow_cloud.md and compare its findings with the three result graphs in assets/2016-02-11-m3xl.png, assets/2016-02-11-m32xl.png, and assets/2016-02-11-c38xl.png. Investigate the reported c3.8xl network behavior and whether Ansible startup timing affects the 7–8 second target, but the issue does not define a concrete completion condition.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ansible
- Domain
- distributed-systems, documentation, performance
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100