Questo sito utilizza cookie di profilazione (propri e di terze parti) per ottimizzare la tua esperienza online e per inviarti pubblicità in linea con le tue preferenze. Continuando a utilizzare questo sito senza modificare le tue preferenze acconsenti all’uso dei cookie. Se vuoi saperne di più o negare il consenso a tutti o ad alcuni cookie clicca qui>
The website that you are visiting also provides Arabian language. Do you wish to switch language version?
يوفر موقع الويب الذي تزوره المحتوى باللغة العربية أيضًا. هل ترغب في تبديل إصدار اللغة؟
The website that you are visiting also provides Russia language Do you wish to switch language version?
Данный сайт есть в английской версии. Желаете ли Вы перейти на английскую версию?
The copy on windows is slow, within same LUN, from one directory to another, bandwidth is about 70MB。
1、the action is performed on the LUN ID 3, which belong to storage ID: 3。
The information of Storage pool (3) :
Space of storage pool(3) is going to use up. The left space is only on Tier2( NL SAS), which implies that all the new write IO would performed on NL SAS disk.
2. According to the data distribution on LUN 3: 75% of data is on NL SAS. It is high possible that the data user wants to copy is stored on NL SAS.
3、we check the performance monitor and the read and write bandwidth is about 150MB, that is normal.
based on the analysis above, the copy action is 1:1 read/write, both were performed on NL SAS. Read and write in total is about 140MB/S
And the Disk domain where the LUN located on, had only 5 NL SAS disk . the Storage pool raid is raid10.
And the single NL SAS disk bandwidth performance in theory is 30MB(read)/20MB(write) , So the max performance of the LUN is : read: 5*30MB / write: 5*20MB = 150MB/S in read, and 100MB/S in write.
So, the performance is close to the max performance.
The performance is reasonable .
this is not a problem.