ioDrive2 Duo drive 두개를 DELL T7610에 장착해서 fio-status 커맨드로 상태를 확인 했습니다.
여기서 RAM usage 항목이 두개 각각의 ioDrive2 Duo drive 에 따라서 다르게 나옵니다.
RAM usage 의 의미가 무엇인가요?
이 "RAM usage"는 포맷 설정에 따라 달라지는 것인가요?
"RAM usage" 를 드라이브 마다 동일하게 하려면 어떻게 해야 하나요?
fct0, fct1 RAM usage: Current: 452,976,960 bytes Peak : 452,976,960 bytes fct2, fct3 RAM usage: Current: 1,266,797,760 bytes Peak : 1,266,797,760 bytes
전체 파일은 아래와 같습니다.
Found 4 ioMemory devices in this system with 2 ioDrive Duos Driver version: 3.2.14 build 1675 Adapter: Dual Controller Adapter HP 2410GB MLC PCIe ioDrive2 Duo for ProLiant Servers, Product Number:673648-B21, SN:3UN346F01C ioDrive2 Adapter Controller, PN:674328-001 SMP(AVR) Versions: App Version: 1.0.33.0, Boot Version: 0.0.8.1 External Power: connected PCIe Bus voltage: avg 11.88V PCIe Bus current: avg 1.77A PCIe Bus power: avg 21.02W PCIe Power limit threshold: Disabled PCIe slot available power: 75.00W PCIe negotiated link: 8 lanes at 5.0 Gt/sec each, 4000.00 MBytes/sec total Connected ioMemory modules: fct0: Product Number:673648-B21, SN:1343D04BC-1121 fct1: Product Number:673648-B21, SN:1343D04BC-1111 fct0 Attached SN:1343D04BC-1121 SMP(AVR) Versions: App Version: 1.0.29.0, Boot Version: 0.0.9.1 Located in slot 1 Lower of ioDrive2 Adapter Controller SN:1343D04BC Powerloss protection: protected PCI:06:00.0, Slot Number:2 Vendor:1aed, Device:2001, Sub vendor:1590, Sub device:70 Firmware v7.1.17, rev 116786 Public 1205.00 GBytes device size Format: v500, 2353515625 sectors of 512 bytes PCIe slot available power: 25.00W PCIe negotiated link: 4 lanes at 5.0 Gt/sec each, 2000.00 MBytes/sec total Internal temperature: 45.77 degC, max 61.03 degC Internal voltage: avg 1.02V, max 1.02V Aux voltage: avg 2.49V, max 2.50V Reserve space status: Healthy; Reserves: 100.00%, warn at 10.00% Active media: 100.00% Rated PBW: 17.00 PB, 99.69% remaining Lifetime data volumes: Physical bytes written: 53,073,006,514,880 Physical bytes read : 47,029,857,831,216 RAM usage: Current: 452,976,960 bytes Peak : 452,976,960 bytes Contained VSUs: fioa: ID:0, UUID:1a6c8347-d031-481e-8ae1-36318719655d fioa State: Online, Type: block device ID:0, UUID:1a6c8347-d031-481e-8ae1-36318719655d 1205.00 GBytes device size Format: 2353515625 sectors of 512 bytes fct1 Attached SN:1343D04BC-1111 SMP(AVR) Versions: App Version: 1.0.29.0, Boot Version: 0.0.9.1 Located in slot 0 Upper of ioDrive2 Adapter Controller SN:1343D04BC Powerloss protection: protected PCI:07:00.0, Slot Number:2 Vendor:1aed, Device:2001, Sub vendor:1590, Sub device:70 Firmware v7.1.17, rev 116786 Public 1205.00 GBytes device size Format: v500, 2353515625 sectors of 512 bytes PCIe slot available power: 25.00W PCIe negotiated link: 4 lanes at 5.0 Gt/sec each, 2000.00 MBytes/sec total Internal temperature: 49.22 degC, max 60.54 degC Internal voltage: avg 1.01V, max 1.02V Aux voltage: avg 2.49V, max 2.50V Reserve space status: Healthy; Reserves: 100.00%, warn at 10.00% Active media: 100.00% Rated PBW: 17.00 PB, 99.69% remaining Lifetime data volumes: Physical bytes written: 51,996,792,912,192 Physical bytes read : 45,786,200,526,144 RAM usage: Current: 443,953,920 bytes Peak : 446,387,520 bytes Contained VSUs: fiob: ID:0, UUID:afe87aac-f621-4859-a6fc-13d09df955d4 fiob State: Online, Type: block device ID:0, UUID:afe87aac-f621-4859-a6fc-13d09df955d4 1205.00 GBytes device size Format: 2353515625 sectors of 512 bytes Adapter: Dual Controller Adapter HP 2410GB MLC PCIe ioDrive2 Duo for ProLiant Servers, Product Number:673648-B21, SN:3UN246F07E ioDrive2 Adapter Controller, PN:674328-001 SMP(AVR) Versions: App Version: 1.0.35.0, Boot Version: 0.0.8.1 External Power: connected PCIe Bus voltage: avg 11.81V PCIe Bus current: avg 1.72A PCIe Bus power: avg 20.33W PCIe Power limit threshold: Disabled PCIe slot available power: 75.00W PCIe negotiated link: 8 lanes at 5.0 Gt/sec each, 4000.00 MBytes/sec total Connected ioMemory modules: fct2: Product Number:673648-B21, SN:1242D9426-1121 fct3: Product Number:673648-B21, SN:1242D9426-1111 fct2 Attached SN:1242D9426-1121 SMP(AVR) Versions: App Version: 1.0.29.0, Boot Version: 0.0.9.1 Located in slot 1 Lower of ioDrive2 Adapter Controller SN:1242D9426 Powerloss protection: protected PCI:0b:00.0, Slot Number:4 Vendor:1aed, Device:2001, Sub vendor:1590, Sub device:70 Firmware v7.1.17, rev 116786 Public 1205.00 GBytes device size Format: v500, 2353515625 sectors of 512 bytes PCIe slot available power: 25.00W PCIe negotiated link: 4 lanes at 5.0 Gt/sec each, 2000.00 MBytes/sec total Internal temperature: 45.28 degC, max 61.52 degC Internal voltage: avg 1.01V, max 1.02V Aux voltage: avg 2.49V, max 2.50V Reserve space status: Healthy; Reserves: 100.00%, warn at 10.00% Active media: 100.00% Rated PBW: 17.00 PB, 98.31% remaining Lifetime data volumes: Physical bytes written: 286,868,961,505,072 Physical bytes read : 4,558,699,572,197,304 RAM usage: Current: 1,266,797,760 bytes Peak : 1,266,797,760 bytes Contained VSUs: fioc: ID:0, UUID:55975a23-db01-45ff-9ad9-d8bafb73d0d8 fioc State: Online, Type: block device ID:0, UUID:55975a23-db01-45ff-9ad9-d8bafb73d0d8 1205.00 GBytes device size Format: 2353515625 sectors of 512 bytes fct3 Attached SN:1242D9426-1111 SMP(AVR) Versions: App Version: 1.0.29.0, Boot Version: 0.0.9.1 Located in slot 0 Upper of ioDrive2 Adapter Controller SN:1242D9426 Powerloss protection: protected PCI:0c:00.0, Slot Number:4 Vendor:1aed, Device:2001, Sub vendor:1590, Sub device:70 Firmware v7.1.17, rev 116786 Public 1205.00 GBytes device size Format: v500, 2353515625 sectors of 512 bytes PCIe slot available power: 25.00W PCIe negotiated link: 4 lanes at 5.0 Gt/sec each, 2000.00 MBytes/sec total Internal temperature: 46.26 degC, max 60.54 degC Internal voltage: avg 1.02V, max 1.02V Aux voltage: avg 2.49V, max 2.50V Reserve space status: Healthy; Reserves: 100.00%, warn at 10.00% Active media: 100.00% Rated PBW: 17.00 PB, 98.37% remaining Lifetime data volumes: Physical bytes written: 277,400,080,592,576 Physical bytes read : 4,264,752,733,317,720 RAM usage: Current: 1,274,323,200 bytes Peak : 1,274,323,200 bytes Contained VSUs: fiod: ID:0, UUID:32de5a07-44c0-454a-a44b-7e8918df1401 fiod State: Online, Type: block device ID:0, UUID:32de5a07-44c0-454a-a44b-7e8918df1401 1205.00 GBytes device size Format: 2353515625 sectors of 512 bytes
초보자 ....
구글 검색에서 찾았습니다.
중간 부분쯤에 이런 내용이 나옵니다.
Memory usage in the VSL depends 100% on what blocksize you are WRITING. The memory consumption is just to hold pointers in memory to quickly lookup where data is on the card.
If you are writing at 512B, you will consume a LOT more memory than if you are writing at 4k.
A lot of DB apps/etc require 512B block sizes on the backing store, but they tend to write at 32-64K or larger, which uses very little memory footprint in the VSL.
작은 블럭을 빨리 찾기 위한 포인터를 메모리에 유지해서 사용한다고 하는거 같습니다.
올려주신 결과를 보면 fct0, fct1에 생성된 볼륨에서 4k이상, fct2, fc3은 4k 미만의 작은 블럭들을 처리하는 것으로 짐작됩니다.
fct0, fct1, fct2, fct3 모두
"Format: v500, 2353515625 sectors of 512 bytes"
라고 되어 있어서 모두 512B block sizes 라고 생각 했습니다.
하지만 RAM usage가 다르기 때문에 초기화에서 뭔가 다르게 구성된 것인지 찾아 보는데 알수가 없군요..
님의 회신에 "fct0, fct1에 생성된 볼륨에서 4k이상, fct2, fc3은 4k 미만의 작은 블럭들을 처리하는 것으로 짐작됩니다." 는
위에 있는 fio-status 어떤 차이를 보고 말씀 하시는지요?
그래서 fct2, fc3는 메모리에 1G를 잡아먹는 중이고 fct0, fct1는 400M를 사용중이라서 그렇게 추측을 한 겁니다.
작은 블럭을 많이 사용하면 할 수록 메모리에 포인터를 기록해둬야 하니까요.
소스를 컴파일하는 시스템이거나 아이콘 이미지 처리를 많이 하는 시스템이라 생각했습니다.