similar to: Memory Issue

-- View this message in context: http://r.789695.n4.nabble.com/How-to-define-new-matrix-based-on-an-elementary-row-operation-in-a-single-step-tp2341768p2341768.html Sent from the R help mailing list archive at Nabble.com.

Dear Users, please help with the following DF test: ===== library(tseries) library(timeSeries) Y=c(3519,3803,4332,4251,4661,4811,4448,4451,4343,4067,4001,3934,3652,3768 ,4082,4101,4628,4898,4476,4728,4458,4004,4095,4056,3641,3966,4417,4367 ,4821,5190,4638,4904,4528,4383,4339,4327,3856,4072,4563,4561,4984,5316 ,4843,5383,4889,4681,4466,4463,4217,4322,4779,4988,5383,5591,5322,5404

Does anyone know how to make a plot like Fig. 4 of Paik, et al., New England Journal of Medicine, Dec. 30, 2004? Given survival data and a covariate, they plot a curve giving "Rate of Distant Recurrence at 10 Yr (% of patients)" on the y-axis versus the covariate on the x-axis. They also plot curves giving a 95% confidence interval. Thanks very much. -Ben The information in this

I'm looking for software that makes plots such as fig 4 (a)-(e), fig 5 anf fig 7 of Gray, Robert, "Flexible Methods for Analyzing Survival Data Using Splines, with Applications to Breast Cancer Prognosis," 1992, J Am Stat Assoc, pp 942-51. In other words, I'm looking for software that takes survival data and a continuous covariate as input and computes a curve giving log hazard

Hi All I was reading through this: http://kashyapc.com/2011/12/02/little-more-disk-io-perf-improvement-with-fallocateing-a-qcow2-disk/ I was basically searching for pointers on improving disk I/O. I wanted to know the purpose of preallocation=full & preallocation=metadata , What is the difference between them ? and which one would yield a better disk I/O speed ? Appreciate your

Hi All, When I tried to create preallocated image with gluster , I am unable to create one The image gets created but not preallocated. [root@ ]# qemu-img create -f qcow2 -o preallocation=full gluster://host1.lab.eng.blr.redhat.com/rep3vol/vm3.img 3G Formatting 'gluster://dhcp37-61.lab.eng.blr.redhat.com/rep3vol/newvm3.img', fmt=qcow2 size=3221225472 encryption=off cluster_size=65536

When creating qcow2 images using virt-builder, is there a way to specify the qcow2 preallocation, as possible with qemu-img create -o preallocation=metada , for example? TIA, Y.

On Tue, May 17, 2016 at 05:53:31PM +0300, Yaniv Kaul wrote: > On Tue, May 17, 2016 at 5:48 PM, Richard W.M. Jones <rjones@redhat.com> > wrote: > > > On Tue, May 17, 2016 at 03:41:53PM +0100, Richard W.M. Jones wrote: > > > On Tue, May 17, 2016 at 05:15:57PM +0300, Yaniv Kaul wrote: > > > > When creating qcow2 images using virt-builder, is there a way to

On Tue, May 17, 2016 at 03:41:53PM +0100, Richard W.M. Jones wrote: > On Tue, May 17, 2016 at 05:15:57PM +0300, Yaniv Kaul wrote: > > When creating qcow2 images using virt-builder, is there a way to specify > > the qcow2 preallocation, as possible with qemu-img create -o > > preallocation=metada , for example? > > No .. but .. it does default to preallocation=metadata

A lot of code runs 'qemu-img create' or 'truncate' to create blank disk images. In the past I resisted adding an API to do this, since it essentially duplicates what you can already do using other tools (ie. qemu-img). However this does simplify calling code quite a lot since qemu-img is somewhat error-prone to use (eg: don't try to create a disk called "foo:bar")

We previously implicitly supported writing to block devices instead of local files, but there were several problems: * Block devices could be deleted, especially if virt-v2v failed during a conversion. * Block devices could be overwritten by a file with the same name, although I believe this is just an observed consequence of the previous point, or at least I was not able to reproduce this

Hi Timo, Any chance the mbox/mdbox writer code could be modified to do physical preallocation on files to help avoid file(system) fragmentation? Constantly appending a file is the prime recipe for causing fragmentation, and mbox is notorious for this--not a fault of Dovecot but the nature of the mbox beast. Obviously maildir doesn't have such a problem, but some (many?) of us still prefer

Greets, I have to research performance-issues of a W2003-VM within KVM. Right now it's a qcow2-image-file w/ default settings within libvirt (configured by vmm ...) My question: what caching to use? writeback/writethrough/etc ... what to use for data integrity while not getting ultraslow performance? Found https://www.linuxfoundation.jp/jp_uploads/JLS2009/jls09_hellwig.pdf Is there

Wayne.my vote is for a command-line option. I've noticed there is some penalty for very large files (35GB-50GB). The penalty is relatively small based on my 'intuitive' measurements.read me watching without running a real timer. The difference is very small compared to what happens after a few weeks without the fragmentation patch. Our SAN was becoming so fragmented that we were

On Tue, Sep 01, 2020 at 08:55:38PM +0300, Nir Soffer wrote: ... > > Note this commit intentionally does not prevent you from writing qcow2 > > to a block device. RHV uses this so it is a thing that people do. ... > > +Note that you must create block devices of the correct size, and you > > +need to use I<-of raw> since other output formats would not normally >

For raw, this allows "off" as a synonym for "sparse" (to make it consistent with qcow2). For qcow2, this allows "sparse" as a synonym for "off". It also adds qcow2 "full" preallocation, which is actually mapped to the qemu option "falloc" (see arguments about this on the qemu-devel mailing list, which we lost). This also updates the

Factor out copying the overlays to final disk images into a separate function. Signed-off-by: Roman Kagan <rkagan@virtuozzo.com> --- v2v/v2v.ml | 227 +++++++++++++++++++++++++++++++------------------------------ 1 file changed, 114 insertions(+), 113 deletions(-) diff --git a/v2v/v2v.ml b/v2v/v2v.ml index afffde2..703038c 100644 --- a/v2v/v2v.ml +++ b/v2v/v2v.ml @@ -110,121 +110,9 @@ let

I have a script that syncs my backups to an NFS mount every day The script works fine, without any errors, but there is a problem when it comes to some large files Let's take my pst file (8.9 gig) as an example Source: du -hs mypst.pst 8.9G mypst.pst ls -alh mypst.pst -rw-rw---- 1 me me 8.9G Jan 25 17:07 mypst.pst That seems OK Let's do that on the destination: du -hs mypst.pst

On Tue, Dec 12, 2017 at 07:55:55PM +0800, Wei Wang wrote: > +int xb_preload_and_set_bit(struct xb *xb, unsigned long bit, gfp_t gfp); I'm struggling to understand when one would use this. The xb_ API requires you to handle your own locking. But specifying GFP flags here implies you can sleep. So ... um ... there's no locking? > +void xb_clear_bit_range(struct xb *xb, unsigned

On Tue, Dec 12, 2017 at 07:55:55PM +0800, Wei Wang wrote: > +int xb_preload_and_set_bit(struct xb *xb, unsigned long bit, gfp_t gfp); I'm struggling to understand when one would use this. The xb_ API requires you to handle your own locking. But specifying GFP flags here implies you can sleep. So ... um ... there's no locking? > +void xb_clear_bit_range(struct xb *xb, unsigned