search for: xnz

Hi, For this example: O <- c(0 0 0 2 0 0 2 0) I want to create an array every time O[i] > 0. The array should be in the form; R[j] <- array(-1, dim=c(2,O[i])) i.e. if O[i] > 0 4 times I want 4 R arrays. Does anyone have any suggestions? Thanks, Doug -- View this message in context: http://r.789695.n4.nabble.com/Create-Arrays-tp2996706p2996706.html Sent from the R help

Hi, I just noticed something interesting ... don''t know whether it''s relevant or not (two commands run in succession during a ''nightly'' run): $ iostat -xnz 6 [...] extended device statistics r/s w/s kr/s kw/s wait actv wsvc_t asvc_t %w %b device 0.0 0.3 0.0 0.8 0.0 0.0 0.2 0.2 0 0 c2t0d0 2.2 79.8 128.7 216.1 0.0 0.1 0.1 1.4 1 6 c1t0d0 2.0 76.8 118.1 208.6 0.0...

...nt+0x9b0(2a10069f8b0, 1, 600225f6080, 0, 0, 0) 000002a10069f121 mount+0x110(600013fbcf8, 2a10069fad8, 0, 0, ff38e40c, 100) 000002a10069f221 syscall_ap+0x44(2a0, ffbfeca0, 1118bf4, 600013fbc40, 15, 0) 000002a10069f2e1 syscall_trap32+0xcc(52b3c8, ffbfeca0, 100, ff38e40c, 0, 0) > # iostat -xnz 1 extended device statistics r/s w/s kr/s kw/s wait actv wsvc_t asvc_t %w %b device 3.0 513.0 192.0 2822.1 0.0 2.1 0.0 4.0 0 95 c4t600C0FF00000000009258F3E4C4C5601d0 extended device statistics r/s w/s kr/s kw/s wait ac...

...5.69G 266G 23 76 1.44M 2.24M pool1 5.69G 266G 96 259 5.70M 7.25M pool1 5.69G 266G 98 267 5.73M 7.32M pool1 5.69G 266G 92 253 5.76M 7.31M pool1 5.69G 266G 90 254 5.67M 7.43M and here is regular iostat: # iostat -xnz 5 extended device statistics r/s w/s kr/s kw/s wait actv wsvc_t asvc_t %w %b device 0.0 0.2 0.0 0.1 0.0 0.0 0.0 0.3 0 0 c0t0d0 0.0 0.2 0.0 0.1 0.0 0.0 0.0 0.3 0 0 c0t1d0 20.4 145.0 1315.8 3714.5 0.0 2.8 0.0 1...

...t, but same drive). dd''ing from the device though is no problems, as long as I''m not trying to read from the pool. When the pool is in it''s very slow/hung state, you can''t do anything with the devices. Here''s my devices: tim at opensolaris:~$ iostat -xnz extended device statistics r/s w/s kr/s kw/s wait actv wsvc_t asvc_t %w %b device 1.5 2.7 98.1 29.4 0.1 0.0 18.6 8.3 1 2 c0d0 3.9 0.6 220.9 57.9 0.0 0.0 5.6 1.2 0 0 c6d1 8.1 0.0 456.8 0.0 0.0 0....

...ted config: NAME STATE READ WRITE CKSUM f3-2 ONLINE 0 0 0 c2t42d0 ONLINE 0 0 0 c2t42d1 ONLINE 0 0 0 c2t42d2 ONLINE 0 0 0 errors: No known data errors bash-3.00# iostat -xnz 1 [...] extended device statistics r/s w/s kr/s kw/s wait actv wsvc_t asvc_t %w %b device 0.0 16.2 0.0 35.4 0.0 0.1 0.0 3.7 0 2 c2t42d2 0.0 31.3 0.0 634.3 0.0 0.1 0.0 4.1 0 3 c2t42d1 exte...

...er-9 761G 19.3T 437 186 7.92M 281K thumper-9 761G 19.3T 452 259 4.07M 371K thumper-9 761G 19.3T 592 321 9.43M 460K thumper-9 761G 19.3T 421 196 8.25M 254K thumper-9 761G 19.3T 550 201 22.6M 290K ^C bash-3.00# But: bash-3.00# iostat -xnz 1 [removed first output] extended device statistics r/s w/s kr/s kw/s wait actv wsvc_t asvc_t %w %b device 25.1 0.0 904.7 0.0 0.0 0.1 0.8 5.9 2 15 c4t0d0 20.1 0.0 711.0 0.0 0.0 0.1 0.0 5.9 0 12 c6t0d0 23.1 0.0 776.3...

Under Solaris 10 on a 4 core Sun Ultra 40 with 20GB RAM, I am setting up a Sun StorageTek 2540 with 12 300GB 15K RPM SAS drives and connected via load-shared 4Gbit FC links. This week I have tried many different configurations, using firmware managed RAID, ZFS managed RAID, and with the controller cache enabled or disabled. My objective is to obtain the best single-file write performance.

In order to get more information on IO performance problems I created the script below: #!/usr/sbin/dtrace -s #pragma D option flowindent syscall::*write*:entry /pid == $1 && guard++ == 0/ { self -> ts = timestamp; self->traceme = 1; printf("fd: %d", arg0); } fbt::: /self->traceme/ { /* elapsd =timestamp - self -> ts; printf("

...JNX12GVo9RupQIo7SP7UGYMhnIRQuOd23P8Q/hpZdRuEtY5ksx I5k8qSMSgFWzj5SRgjPrjj8qkbSbRs8TAlt25biRWzjHUNnnAz645pZdLtZYIoW84JEcrsuJFOc5 ySGyTnnJzVXj/X/DiKt5q1zaCGN7INcyBmKo0joFBHOVjJ5yOqjv7Zv2Nybu0jnaGSFmzlJFKkEH HQgHHpwOKbLp9vNDHG/m/uvuuJnDj/gYO4/nU0EK28QiQuVHQySM5/NiSaTcbabgV9Tnnt7UyQIr AEbyX2kD1HykE+xxRfXNzBJbpbW0cxmYr88pTaQCf7p44P6U+9sYL5Alx5u0dkmeMH67SM/jTf7O t/3GTOTASUJuJCcn1O7n8c0k421GVL28vX0uKW0jjjllkWNt0mNhLBTg7SDz3I98dqkSW+t4Ybcq tzeOGZjJMAoAP95UGeo/hp7aRaNbJbn7R5aNvUC5kBznOc7snnmpJNOt5IY4mM2I87XE7hxnr84O 4/ifSqvHYRBLqNwlrHMlmJHMnlSRiUAq2cfKSMEZ9ccflUdzqd/a7fM0+Jv3byPsuc4CkZxlRngj Gcc56dTZl0u1l...

Hi!We''re trying to pinpoint our performance issues and we could use all the help to community can provide. We''re running the latest version of Nexenta on a pretty powerful machine (4x Xeon 7550, 256GB RAM, 12x 100GB Samsung SSDs for the cache, 50GB Samsung SSD for the ZIL, 10GbE on a dedicated switch, 11x pairs of 15K HDDs for the pool). We''re connecting a single Linux