search for: 452m

...937M llvm-c-test 653M clang-import-test 512M clangd 493M arcmt-test 484M lli 480M clang-query 473M clang-refactor 469M clang-move 468M global-symbol-builder 467M clang-change-namespace 464M tool-template 464M clang-rename 462M clang-reorder-fields 460M find-all-symbols 456M clang-doc 452M clang-include-fixer 444M modularize 443M clang-func-mapping 442M clang-diff 441M libToolingExample00 438M pp-trace 434M diagtool 184M llvm-cfi-verify 170M llvm-objdump 168M sancov 158M llvm-rtdyld 149M llvm-ar 148M llvm-nm 145M llvm-extract 145M llvm-link 142M llvm-dwarfdump 141M ll...

...arcmt-test > 484M lli > 480M clang-query > 473M clang-refactor > 469M clang-move > 468M global-symbol-builder > 467M clang-change-namespace > 464M tool-template > 464M clang-rename > 462M clang-reorder-fields > 460M find-all-symbols > 456M clang-doc > 452M clang-include-fixer > 444M modularize > 443M clang-func-mapping > 442M clang-diff > 441M libToolingExample00 > 438M pp-trace > 434M diagtool > 184M llvm-cfi-verify > 170M llvm-objdump > 168M sancov > 158M llvm-rtdyld > 149M llvm-ar > 148M llvm-nm >...

...tem. I''m trying to index a really big folder containing lots of files (18M), the disk size is ~220Gig. The files are quite small text files (mean size ~ 1K). The OS is latest leopard. I think the process is io-bound. 63061 recollinde 10.4% 3:58:06 1 15 486 435M 188K 435M 452M I''m using those 2 scripts found here: http://www.sun.com/software/solaris/howtoguides/dtracehowto.jsp#3 #!/usr/sbin/dtrace -qs BEGIN { printf("%10s %58s %2s\n", "DEVICE", "FILE", "RW"); } io:::start { printf("%10s %58s %2s\n", args[...

...;ve manuelly added tun99 to trap the packets: [root@perack ~]# iptables -L FORWARD -v Chain FORWARD (policy DROP 4 packets, 366 bytes) pkts bytes target prot opt in out source destination 677K 448M eth0_fwd all -- eth0 any anywhere anywhere 417K 452M tun_fwd all -- tun+ any anywhere anywhere 294 34569 tun99_fwd all -- tun99 any anywhere anywhere 1600 696K eth1_fwd all -- eth1 any anywhere anywhere 244K 67M eth3_fwd all -- eth3 any anywhere anywhere...

Hi Guys, My users are reporting some issues with memory on our lustre 1.8.1 clients. It looks like when they submit a single job at a time the run time was about 4.5 minutes. However, when they ran multiple jobs (10 or less) on a client with 192GB of memory on a single node the run time for each job was exceeding 3-4X the run time for the single process. They also noticed that the swap space