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.

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

Workload and Power Parameters #13

Open
daliasobhi opened this issue Feb 6, 2018 · 0 comments
Open

Workload and Power Parameters #13

daliasobhi opened this issue Feb 6, 2018 · 0 comments

Comments

@daliasobhi
Copy link

Hello Harsh,

I would like to thank you for the amazing fog computing simulator, which was a great add-on to my research.

But I have some questions related to the simulator to be able to fully use it:
1- From where have you got the parameters for the smart camera example, for instance, the network latency = 100ms ?
2- In scalability experiments, it was mentioned that the workload has been varied by emitting the tuple of Headset A at twice the rate of Headset B, how did you do that? Because I am trying to vary the workload, but failed to do that.
3- From where are the CPU power values for the smart camera case are conducted ? I have searched a lot for the past couple of weeks, but couldn’t reach a solution.
4- Same applies to the tuple size, from where have you assumed the values?
5- I want to generate workload to test the proposed application under different environmental conditions. For instance, what will be the application delay, if the number of requests are equal to 1000,2000, and so on. I tried to vary the number of cloud users to millions but the application loop delay was the same.
6- How to have fluctuations in energy consumption and application loop delay without changing the configuration (ex. two gateways, each with 4 smart cameras).

Thank you so much Harsh

Wishing you the best

Best Regards
Dalia

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant