Skip to content
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.

Sign up for GitHub

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

Jump to bottom

CodeRefactoring: compute processing load at init #73

Closed
3 tasks done
ale93p opened this issue Feb 13, 2019 · 0 comments · Fixed by #133
Closed
3 tasks done

CodeRefactoring: compute processing load at init #73

ale93p opened this issue Feb 13, 2019 · 0 comments · Fixed by #133
Labels
Platform: All The issue is related to all the applications Priority: Low The issue is secondary Type: Enhancement Improvement of existing feature

Comments

@ale93p
Copy link
Owner

ale93p commented Feb 13, 2019 •
edited

Use the same model as for the components parallelism, this would avoid to perform the computation each time:

  • Create a computeComponentsProcessing and store the values into an ArrayList
  • Create a getComponentsProcessing that returns the array
  • Implement the iterator in the main application
@ale93p ale93p added Type: Enhancement Improvement of existing feature Priority: Medium labels Feb 13, 2019
@ale93p ale93p mentioned this issue Feb 13, 2019
Open
@ale93p ale93p changed the title Application: compute processing load at init CodeRefactoring: compute processing load at init Feb 13, 2019
@ale93p ale93p added the Platform: All The issue is related to all the applications label Feb 18, 2019
@ale93p ale93p added Priority: Low The issue is secondary and removed Priority: Medium labels Mar 8, 2019
@ale93p ale93p added this to the Release 1.0.0 milestone Mar 8, 2019
@ale93p ale93p removed this from the Release 1.0.0 milestone Aug 7, 2019
ale93p added a commit that referenced this issue Feb 18, 2020
@ale93p
[AppBuilder] Compute Processing Load at init (Closes #73)
2b5d100
@ale93p ale93p mentioned this issue Feb 18, 2020
Merged
ale93p added a commit that referenced this issue Mar 16, 2020
@ale93p
[WIP] [v0.7.2] Fix logging (#133)
f480d46 
* [AppBuilder] Compute Processing Load at init (Closes #73)

* [Storm & Flink] Refactored BenchmarkApplication component: splitted TopologyBuilder
*  Fixed tuple logging: now tuples are sampled based on source count and not local one. This assure to have printed always the same tuples, better for latency computation.

* [v0.7.2] Bump Version
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Platform: All The issue is related to all the applications Priority: Low The issue is secondary Type: Enhancement Improvement of existing feature
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

[v0.7.2] Fix logging ale93p/namb
1 participant
@ale93p