search for: 193k

...icients of model fits? For example, I've run a glm fit that has 23 coefficents on data set that had 193,008 rows, by the time the fit was called. When I save the resulting fit object, I get a 491 MB object, which suggests that it's pulling along all sorts of junk in the environment, as 23*193k*8 is only 34 MB. Even so, I would prefer to only save the coefficients and the Hessian, not the fit data set. Is there anything I can do? If I want to save several fits, 490 MB a shot starts to add up very quickly. If I just save the coefficients, I have to manually hack up an object that I can...

...quadcore VM and run fio inside the VM, and num_queues of the virtio-blk device is set as 2, but looks the improvement is still obvious. 1), about scalability - without mutli-vq feature -- jobs=2, thoughput: 145K iops -- jobs=4, thoughput: 100K iops - with mutli-vq feature -- jobs=2, thoughput: 193K iops -- jobs=4, thoughput: 202K iops 2), about thoughput - without mutli-vq feature -- thoughput: 145K iops - with mutli-vq feature -- thoughput: 202K iops So in my test, even for a quad-core VM, if the virtqueue number is increased from 1 to 2, both scalability and performance can get improve...

...quadcore VM and run fio inside the VM, and num_queues of the virtio-blk device is set as 2, but looks the improvement is still obvious. 1), about scalability - without mutli-vq feature -- jobs=2, thoughput: 145K iops -- jobs=4, thoughput: 100K iops - with mutli-vq feature -- jobs=2, thoughput: 193K iops -- jobs=4, thoughput: 202K iops 2), about thoughput - without mutli-vq feature -- thoughput: 145K iops - with mutli-vq feature -- thoughput: 202K iops So in my test, even for a quad-core VM, if the virtqueue number is increased from 1 to 2, both scalability and performance can get improve...

...> num_queues of the virtio-blk device is set as 2, but looks the > improvement is still obvious. > > 1), about scalability > - without mutli-vq feature > -- jobs=2, thoughput: 145K iops > -- jobs=4, thoughput: 100K iops > - with mutli-vq feature > -- jobs=2, thoughput: 193K iops > -- jobs=4, thoughput: 202K iops > > 2), about thoughput > - without mutli-vq feature > -- thoughput: 145K iops > - with mutli-vq feature > -- thoughput: 202K iops Of these numbers, I think it's important to highlight that the 2 thread case is 33% faster and the...

https://bugzilla.netfilter.org/show_bug.cgi?id=1101 Bug ID: 1101 Summary: SET target unreliable in iptables - add does not work as expected Product: netfilter/iptables Version: unspecified Hardware: x86_64 OS: Debian GNU/Linux Status: NEW Severity: major Priority: P5

Sep 21 08:57:54 belle fsck: /dev/ad4s1d: 1 DUP I=190 Sep 21 08:57:54 belle fsck: /dev/ad4s1d: UNEXPECTED SOFT UPDATE INCONSISTENCY; RUN fsck MANUALLY. Ok, so I ran fsck manually (even with -y), but yet it refuses to clear/fix whatever to the questions posed as fsck runs. What does this all mean? Thanks, -Clint -- This message has been scanned for viruses and dangerous content by MailScanner,

...-img create -f qcow2 -b testimage2.qcow2 backup-test2.qcow2 Formatting 'backup-test2.qcow2', fmt=qcow2 size=53687091200 backing_file='testimage2.qcow2' encryption=off cluster_size=65536 lazy_refcounts=off # ls -lsh backup-test2.qcow2 196K -rw-r--r-- 1 root root 193K Jun 22 22:48 backup-test2.qcow2 Though perhaps if I actually tried to add them and boot it up something would not work? Keelan On Wed, 22 Jun 2016 09:58:29 +0100 "Richard W.M. Jones" <rjones@redhat.com> wrote: > On Wed, Jun 22, 2016 at 12:40:40AM -0500, > libvirt_us...

On Wed, Jun 22, 2016 at 12:40:40AM -0500, libvirt_users@skagitattic.com wrote: > So you are saying when I do the virt-sparsify its converting the image > from raw to [qcow2]? No. virt-sparsify will use the same input and output formats, unless you use the --convert option. > I studied the man page for virt-sparsify and tried again with > the flag "--format raw"

Joseph Little wrote: > I''d love to "vote" to have this addressed, but apparently votes for > bugs are no available to outsiders. > > What''s limiting Stanford EE''s move to using ZFS entirely for our > snapshoting filesystems and multi-tier storage is the inability to > access .zfs directories and snapshots in particular on NFSv3 clients.