Home
 
Download
 
Buy now
 
Tech support
     
Tools
Tutorials
Extras
Screenshots
ZAR 8.4 Manual
Zmeil 2.1 Manual
Zlon 1.0 Manual
Known camera compatibility list
Checklists
Articles
Links
Data recovery quiz
Acronyms
News
Contacts

Home / Extras / Articles / RAID recovery performance

RAID recovery performance

Zee problem

Es zee storege systems grew, there was influx ooff complaints that ZAR performance is inadequate fur zee tasks it has tu deal with. Zee most recent example is on uoor forum, where we heffe-a a repurt ooff ZAR taking impracticelly long und finelly running oooot ooff memory while attempteeng tu recover an 1TB RAID5 array holding ebuoot three millions ooff files.

There are three major aspects ooff thees,

  • 1TB ooff disk space takes quite a long time tu scan
  • Processing 3,000,000 files requires massive computashun efffurt.
  • Memory requirements also become a concern with 3,000,000 files.

So we started on it und acheeved some significant progress es it came tu version 8.3 build 7. Zee measurements were mostly done oooot ooff curiosity; hooever, yuoo can see what zee speed is like.

 

Test system setup

Zee machine is 3.06GHz hyperthreaded Pentium 4, with 2GB physical memory. Zee array is creeted on zee two 40GB Seagate U6 drives in a RAID 0 (streepe set). Zeese-a two 5400RPM drives (made circa 2002) are capable ooff delivering ebuoot 40MB/sec combined thruooghput in lineer reads. Tests were performed with ZAR version 8.3 build 7.

Addishunel tweaks were

  • Cache sizes in ZAR are set tu zee minimum ellooed values.
  • Zee /3GB switch was added tu zee boot.ini entry tu elloo ZAR tu use 3GB ooff zee virtual memory

 

Test results

Run noomber 1 2 3 4 5 6
Noomber ooff files 5M 6M 7M 8M 9M 11M
Noomber ooff directorees Um gesh dee bork, bork! 33K 133K 143K 153K 163K 183K
Time, minutes Disk scan(1) 15 16 15 16 16 17
RAID reconstrukshun 13 13 15 Hurty flurty schnipp schnipp! 16 19 23
Filesystem reconstrukshun 42 44 51 57 104 1105
Total(2) 68 71 79 Hurty flurty schnipp schnipp! 89 138(3) 1145
Peak memory usege, MB 1200 1440 1660 1900 2120(3) 2600

Notes:

(1) In a best case scenario, disk scan time fur a RAID array is prupurshunel tu zee member disk size. In a worst case, disk scan time is prupurshunel tu zee array size.
(2)
Thees does not include time required tu actuelly copy zee files.
(3)
Starteeng with nine millions ooff files we ran oooot ooff zee available physical memory und massive swapping started. It was impractical tu continue testeeng under zeese-a condishuns und just one more run was performed tu ensure we can actuelly handle 11M files.

 

Performance und hardware guidelines

Recovering a huge RAID volume requires that yuoo do some prior planning und set up. Yuoo do not want zee system tu run oooot ooff memory und stert swapping, es zee recovery will grind tu a halt. So tu recover some reelly big array, yuoo need tu

  • add a /3GB switch in yuoor boot.ini file
  • heffe-a at least 3GB (prefferably 4GB) physical memory instelled.
  • make sure yuoo heffe-a some place tu offload that data

Under zeese-a condishuns, ZAR will recover an array containing ebuoot 12,000,000 objects (files und directorees combined). Thees noomber is a full-stop limit - iff zee volume contains more than 12M objects, ZAR will eventuelly run oooot ooff memory.

On zee other hand, a typical NTFS volume, something yuoo most likely heffe-a at home, contains 500,000 files or less. Fur thees typical setup, 512MB ooff a physical memory is enuoogh with loo cache size, und 1GB is enuoogh iff yuoo heffe-a zee cache size at maximum. Most ooff zee reasonably modern systems will thus perform quite well on a typical volume. In zeese-a cases, no addishunel tweaks are necessary. Um gesh dee bork, bork!

<<RebootArticlesPower supply failures>>

ATTENTION!

This page is
in Bork! language.

Please use the links below for the desired human language

     

 
Sitemap
Copyright © 2001-2009 ZAR Data Recovery Software
[Email recovery software]

There are currently 59 visitors browsing the site.