Improve eDirectory Disk on Azure

0 Likes
6 months ago

Tests performed.

For the tests that were performed:

  • Write tests using the command
    • The command was used:
      • dd if=/dev/zero of=/filesystemtotest/iotest.log bs=64k count=8k conv=fdatasync
    • Write tests using directory objects
      • 50,000 objects were modified only by changing the description attribute.
      • The write/read Azure cache is left on.
      • Three control tests were performed only using a single p10-type disk
      • Three control tests were performed using the 5-disk p10 array.

 

Control test

Write test dd command:

 

/home/novell # dd if=/dev/zero of=/mnt/iotest.log bs=64k count=8k conv=fdatasync

8192 0 records in

8192 0 records out

536870912 bytes (537 MB, 512 MiB) copied, 5.685 s, 94.4 MB/s

 

Proof of writing objects tothe directory

 

50,000, 1 modified attribute 1 authentication per second, 1 P10, azure cache read on and write on

Duration of freezing in seconds

Total execution time mm: ss

28, 12,*

8m31s

26, 13, *

8m24s

24, 15, *

8m26s

 

 

 

 

Stripped test

Write test dd command:

 

/home/novell # dd if=/dev/zero of=/nds/iotest.log bs=64k count=8k conv=fdatasync

8192 0 records in

8192 0 records out

536870912 bytes (537 MB, 512 MiB) copied, 0.429201 s, 1.3 GB/s

 

 

50,000, 1 modified attribute. 5 disk arrange, 1 authentication per second P10, azure chace read on and write on

 

Duration of freezing in seconds

Total execution time mm: ss

1.546s

3m21.752s

1.604s

2m40.691s

1.425s

2m55.051s

Conclusion

Using thetripped array s in conjunction with the caches on shows an undeniable improvement. But this improvement should always be accompanied by backups via  dsbk  or azure images.

 

It is always important to validate that Azure caches are turned on.

 

Comment List
Anonymous
Related Discussions
Recommended