search for: 90m

...ngle IP on it. I created a NFS filesystem for vmware by using : zfs create SSD/vmware . I had to set permissoins for Vmware anon=0, but thats it. Below is what zpool iostat reads: File copy 10Gbe to SSD -> 40M max file copy 1gbe to SSD -> 5.4M max File copy SAS to SSD internal -> 90M File copy SSD to SAS internal -> 55M Top shows not matter what I always have 2.5 G free and every other test says the same thing. Can anyone tell me why this is seems to be slow? Does 90M mean MegaBytes or MegaBits? Thanks, Derek -- This message posted from opensolaris.org

Is there a way to efficiently read large datasets directly into a matrix byrow? I know data.frame, but for large datasets it doesn't efficiently work, also if I increase the cons memory. R --nsize 1000k --vsize 90M ... > x<-read.table("pendler.luft.txt") Error: cons memory (1000000 cells) exhausted See "help(Memory)" on how to increase the number of cons cells. > Also the following is problematic: R --nsize 1000k --vsize 90M ... > x<-scan("pendler.luft.txt&quot...

howdy gurus, I'm new and green and I was hoping for a tiny bit of your expertise. I'm running out of virtual memory (heap?) when summing using tapply. I've already used --vsize=90M on my hpux machine. (details below) Can I pre-sort or something to prevent my error? thanks, John Strumila john.strumila at corpmail.telstra.com.au > gc()["Vcells","total"] [1] 11796480 > gcinfo(TRUE) [1] FALSE > t1<-tapply(trace$elapsed,list(trace$pid,trace$hv,...

...llvm-pdbutil 126M clang-offload-bundler 122M llvm-mca 121M verify-uselistorder 121M llvm-cat 120M llvm-as 117M llvm-special-case-list-fuzzer 117M llvm-demangle-fuzzer 116M llvm-modextract 114M obj2yaml 112M llvm-xray 105M sanstats 105M llvm-symbolizer 96M llvm-readobj 93M llvm-cov 90M lli-child-target 86M llvm-cxxdump 85M llvm-objcopy 83M llvm-cvtres 82M llvm-size 76M clang-apply-replacements 75M clang-format 64M llvm-diff 59M llvm-dis 53M llvm-stress 50M llvm-tblgen 48M llvm-profdata 31M yaml2obj 17M clang-tblgen - regards, Manuel -------------- nex...

...M verify-uselistorder > 121M llvm-cat > 120M llvm-as > 117M llvm-special-case-list-fuzzer > 117M llvm-demangle-fuzzer > 116M llvm-modextract > 114M obj2yaml > 112M llvm-xray > 105M sanstats > 105M llvm-symbolizer > 96M llvm-readobj > 93M llvm-cov > 90M lli-child-target > 86M llvm-cxxdump > 85M llvm-objcopy > 83M llvm-cvtres > 82M llvm-size > 76M clang-apply-replacements > 75M clang-format > 64M llvm-diff > 59M llvm-dis > 53M llvm-stress > 50M llvm-tblgen > 48M llvm-profdata > 31M yaml2ob...

...0M In the guest domain when i checked the following commands i got the output as [root@fedora ~]# df -H Filesystem Size Used Avail Use% Mounted on /dev/sda6 2.2G 904M 1.2G 46% / none 135M 0 135M 0% /dev/shm /dev/sda5 102M 90M 7.2M 93% /lib/modules [root@fedora ~]# fdisk -l Disk /dev/sda7: 1073 MB, 1073741824 bytes 255 heads, 63 sectors/track, 130 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk /dev/sda7 doesn''t contain a valid partition table Disk /dev/sda6: 10.7 GB, 10737418240 bytes 255...

...-> dom0 86.9 Mbits/sec domU --> iBook 87.1 Mbits/sec iBook --> domU 1.87 Mbits/sec The last entry has me baffled. Why would it be so incredibly slow in one direction but not the other? I decided to run some UDP tests as well. server: iperf -s -u -i 1 client: iperf -c server_ip -u -b 90M -t 5 The packet loss is as follows: domU --> domU 0% (using 127.0.0.1) domU --> domU 0% (using domU eth0 IP address) dom0 --> domU ~100% (only 7 of 38464 made it!) domU --> dom0 0.09% dom0 --> iBook 4.7% iBook --> dom0 0.33% domU --> iBook 11% iBook --> domU 1.6% T...

...-> dom0 86.9 Mbits/sec domU --> iBook 87.1 Mbits/sec iBook --> domU 1.87 Mbits/sec The last entry has me baffled. Why would it be so incredibly slow in one direction but not the other? I decided to run some UDP tests as well. server: iperf -s -u -i 1 client: iperf -c server_ip -u -b 90M -t 5 The packet loss is as follows: domU --> domU 0% (using 127.0.0.1) domU --> domU 0% (using domU eth0 IP address) dom0 --> domU ~100% (only 7 of 38464 made it!) domU --> dom0 0.09% dom0 --> iBook 4.7% iBook --> dom0 0.33% domU --> iBook 11% iBook --> domU 1.6% T...

...gt;: an integer number of seconds before we should give up -interactive: puts you into interactive mode. See the tutorial for more details ... ... Exception: java.lang.ThreadDeath thrown from the UncaughtExceptionHandler in thr ead "Thread-8" ←[31mGiven I am viewing the admin page←[90m # features/simple_example.rb:6←[ 0m←[0m ←[31m Error while running >>java -jar "c:/jruby-1.7.3/lib/ruby/gems/shared/ gems/webrat-0.7.3/vendor/selenium-server.jar" -port 4444 -timeout 5 &<< (Runtime Error)←[0m -- You received this message because you are subscrib...

...orld (stable/9) but appears also on pre-compiled 9.1-PRERELEASE. I did not test 9.0-RELEASE. If I do not use rsync on this NFS share, everything works completely fine. Workaround: Use rsync over SSH. --Norbert [1] http://lbo.spheniscida.de/Files/nfs-rsync-crash.tgz (25K), vmcore of around 300M (90M gzipped, 64M LZMA'd) not included

...my objdir for a release build of llvm and clang is >> 3.5G, and a full checkout (workdir + .git dirs) of llvm and clang is >> 0.65G. >> >> If the 1.2G really is a problem for you (or more likely, your >> automated infrastructure), a shallow clone [3] takes this down to 90M. >> >> The critical point to me in all this is that it's easy to set up the >> monolithic repository to appear like it's a bunch of separate repos. >> But it is impossible, insofar as I can tell, to do the opposite. That >> is, option (b) is strictly more powe...

...sitory [2] is 1.2GB. By way of comparison, my objdir for a release build of llvm and clang is 3.5G, and a full checkout (workdir + .git dirs) of llvm and clang is 0.65G. If the 1.2G really is a problem for you (or more likely, your automated infrastructure), a shallow clone [3] takes this down to 90M. The critical point to me in all this is that it's easy to set up the monolithic repository to appear like it's a bunch of separate repos. But it is impossible, insofar as I can tell, to do the opposite. That is, option (b) is strictly more powerful than option (a). Renato has understan...

...devtmpfs devtmpfs 211M 0 211M 0% /dev tmpfs tmpfs 215M 0 215M 0% /dev/shm tmpfs tmpfs 215M 280K 215M 1% /run tmpfs tmpfs 215M 0 215M 0% /sys/fs/cgroup tmpfs tmpfs 215M 0 215M 0% /tmp /dev/mmcblk0p1 vfat 90M 49M 41M 55% /boot tmpfs tmpfs 43M 0 43M 0% /run/user/1000 $ lscpu: Architecture: armv6l Byte Order: Little Endian CPU(s): 1 On-line CPU(s) list: 0 Thread(s) per core: 1 Core(s) per socket: 1 Socket(s): 1 Vendor ID: ARM M...

...way of comparison, my objdir for a release build of llvm and clang is > 3.5G, and a full checkout (workdir + .git dirs) of llvm and clang is > 0.65G. > > If the 1.2G really is a problem for you (or more likely, your > automated infrastructure), a shallow clone [3] takes this down to 90M. > > The critical point to me in all this is that it's easy to set up the > monolithic repository to appear like it's a bunch of separate repos. > But it is impossible, insofar as I can tell, to do the opposite. That > is, option (b) is strictly more powerful than option (a...

Hi everybody, after many weeks of searching/trying, I still can't manage to get vista to use/save roaming profiles with samba as PDC... It has apparently worked a few times in the beginning since the profiles directories are populated. Could it be related to a Vista update or SP1? Here's what I did so far: [HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\System]

We have a 3TB external USB drive that I am trying to attach to some CentOS5 servers. I have tried an older Dell PE1950 and a newer R310 but neither one seems to be able to read the drive. It works no problem on windows servers/workstations and I was able to format with NTFS. I know there are different methods for formatting large disks but this one doesn't even seem to show up as a /dev/

On Sun, Aug 6, 2017 at 4:42 AM, Jim Kusznir <jim at palousetech.com> wrote: > Well, after a very stressful weekend, I think I have things largely > working. Turns out that most of the above issues were caused by the linux > permissions of the exports for all three volumes (they had been reset to > 600; setting them to 774 or 770 fixed many of the issues). Of course, I >