Is it possible to run the workload in parallel?

[anirudhajitani]

From what I know so far, all events are added to the workload and executed serially one by one. Is it possible to change it to simulate multiple parallel requests as it usually happens in real-world?

I had another question about the file size, currently it assumes that all files are of unit length. I plan to add another attribute called file size and make the necessary changes to the caching policies. Is there any other part of the code that I need to take care of to implement this change?

[Lorenzo Saino]

From what I know so far, all events are added to the workload and executed serially one by one. Is it possible to change it to simulate multiple parallel requests as it usually happens in real-world?

No, all requests are atomic, they are completed end to end before a new one begins. To change this you will have to do some implementation work, and I suspect it will very likely slow down execution of experiments. By the way, unless you have specific reasons for needing to run requests concurrently, that will likely not give you any noticeable improvement in the accuracy of results. This paper compared the accuracy of Icarus with other ICN simulators, including ccnSim, that's based on ns-3 and performs packet-level simulations with concurrent requests handling and buffering. The results obtained with ccnSim were pretty identical to those obtained simulating the same scenario with Icarus.

I had another question about the file size, currently it assumes that all files are of unit length. I plan to add another attribute called file size and make the necessary changes to the caching policies. Is there any other part of the code that I need to take care of to implement this change?

You will need to change the workload implementation you want to use so that each event it generates also includes a response size. Apart from that, the only other thing you will need to change is, if you need to measure link load, the implementation of the link load collector so that it takes into account the fact that responses will have different size.

[anirudhajitani]

Hi, Thank you such a quick response. Regards, Anirudha

…

On Sat, Feb 1, 2020 at 11:21 AM Lorenzo Saino ***@***.***> wrote: From what I know so far, all events are added to the workload and executed serially one by one. Is it possible to change it to simulate multiple parallel requests as it usually happens in real-world? No, all requests are atomic, they are completed end to end before a new one begins. To change this you will have to do some implementation work, and I suspect it will very likely slow down execution of experiments. By the way, unless you have specific reasons for needing to run requests concurrently, that will likely not give you any noticeable improvement in the accuracy of results. This paper <https://www.sciencedirect.com/science/article/abs/pii/S1569190X15300654> compared the accuracy of Icarus with other ICN simulators, including ccnSim, that's based on ns-3 and performs packet-level simulations with concurrent requests handling and buffering. The results obtained with ccnSim were pretty identical to those obtained simulating the same scenario with Icarus. I had another question about the file size, currently it assumes that all files are of unit length. I plan to add another attribute called file size and make the necessary changes to the caching policies. Is there any other part of the code that I need to take care of to implement this change? You will need to change the workload implementation <https://github.com/icarus-sim/icarus/blob/master/icarus/scenarios/workload.py> you want to use so that each event it generates also includes a response size. Apart from that, the only other thing you will need to change is, if you need to measure link load, the implementation of the link load collector <https://github.com/icarus-sim/icarus/blob/61066c561d709f444e8d68dfd10326eb3c2e8528/icarus/execution/collectors.py#L225> so that it takes into account the fact that responses will have different size. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#15?email_source=notifications&email_token=AB5AMMKUGQ77SXLAA6ALNILRAWOQDA5CNFSM4KOJLFX2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEKRAYCY#issuecomment-581045259>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AB5AMMJNBQQHUX4NGLUC5HLRAWOQDANCNFSM4KOJLFXQ> .

[Lorenzo Saino]

You're welcome.

[anirudhajitani]

Do you some GlobTraff files I could use?

[Lorenzo Saino]

No, Icarus doesn't ship any GlobeTraff workload files. You will need to download GlobeTraff, build it and generate workload files with you desired parameters.