You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When you have a physical storage device such as an HD, it has a max reading speed. If the HD is attached to a PM, the max transfer rate is such a reading speed, since no network transfer is involved.
When we have a SAN, we continue to have physical storage devices such as HDs or SSDs.
However, for a Host or VM to access a file in the SAN, the file must first be read from the storage device. Only after that, it can be transferred through the network to the destination Host/VM. This means that in fact, the transfer time is not determined by the minimum value between the HarddriveStorage's maxDataRate and the SAN's bandwidth.
Instead, it's the time to read the file from the drive plus the time to transfer the data through the network.
For instance, if we need to transfer a file of 100MB and the speed of the SAN's storage devices is 10MBps, the file will be retrieved from the local drive in 10 seconds. However, if the SAN's bandwidth
is also 10MBps, it will take more 10 seconds to deliver the file to the Host/VM. Considering a network latency of 1 second, it sums up 21 seconds.
Actual behavior
The transfer speed to compute transfer time is considered as the minimum value between the maxTransferRate and the SAN's bandwidth. This way, it's not considering the time to read the file from the drive then the time to transfer it through the network.
If the issue is related to a specific method, provide a test case that fails in order to show the problem
New test cases were added.
Specifications like the version of the project, operating system or workload file used
CloudSim Plus 2.3.4
The text was updated successfully, but these errors were encountered:
manoelcampos
changed the title
Transfer time for SanStorage must be the storage device speed plus the network delay to transfer the file
Transfer time for SanStorage must be the storage device read time plus the network delay to transfer the file
Jun 6, 2018
manoelcampos
changed the title
Transfer time for SanStorage must be the storage device read time plus the network delay to transfer the file
Transfer time for SanStorage must be the storage device read time + the network delay to transfer the file + network latency
Jun 6, 2018
Expected behavior
When you have a physical storage device such as an HD, it has a max reading speed. If the HD is attached to a PM, the max transfer rate is such a reading speed, since no network transfer is involved.
When we have a SAN, we continue to have physical storage devices such as HDs or SSDs.
However, for a Host or VM to access a file in the SAN, the file must first be read from the storage device. Only after that, it can be transferred through the network to the destination Host/VM. This means that in fact, the transfer time is not determined by the minimum value between the HarddriveStorage's maxDataRate and the SAN's bandwidth.
Instead, it's the time to read the file from the drive plus the time to transfer the data through the network.
For instance, if we need to transfer a file of 100MB and the speed of the SAN's storage devices is 10MBps, the file will be retrieved from the local drive in 10 seconds. However, if the SAN's bandwidth
is also 10MBps, it will take more 10 seconds to deliver the file to the Host/VM. Considering a network latency of 1 second, it sums up 21 seconds.
Actual behavior
The transfer speed to compute transfer time is considered as the minimum value between the
maxTransferRate
and the SAN'sbandwidth
. This way, it's not considering the time to read the file from the drive then the time to transfer it through the network.If the issue is related to a specific method, provide a test case that fails in order to show the problem
New test cases were added.
Specifications like the version of the project, operating system or workload file used
CloudSim Plus 2.3.4
The text was updated successfully, but these errors were encountered: