-
Notifications
You must be signed in to change notification settings - Fork 65
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
Roadmap for demo 1 #1
Comments
Congratulations! We have finished this demo. Thank you for watching and participating in it! |
Congrats! What's your plan on the networking stuff? Good news is the industry wholesale transit prices have fallen at least 50% during the past 8 years <though AWS is never part of it ;)> |
We may need some optimizations in the design and implementation. |
@huachaohuang you can link the post of demo 1 in the description https://engula.com/posts/demo-1/ . Congrats! I'm reading it. |
The first question I'd like to ask is that how can I reproduce your demo? You can omit details independent to Engula, like assuming the reader already sets up two Although I can read the report literally, a reproducible steps (could be an appendix to the original report) is interesting to explore. Depend on your schedule and whether retain the history generating the report, you may consider this suggestion. |
@tisonkun Hmm, let me document it somewhere. But I have to say it is cumbersome since I haven't pay attention to the deployment stuff yet. |
I added some guides to run experiments on README. |
We are closing this issue now, thanks for watching and participating in this demo. |
The project is just started and is still in the demo stage now.
The primary goal in this stage is to explore the possibility of our designs.
We plan to release the first demo at the end of Sep 2021.
We are going to achieve the following objectives:
Tasks:
SELECT
However, we are short of hands.
If you think we are behind schedule, please push us with a 👍
Update: this demo has ended, please check the report for more details.
The text was updated successfully, but these errors were encountered: