search for: disproport

Displaying 19 results from an estimated 19 matches for "disproport".

2016 Dec 13
2
LLD status update and performance chart
Hal Finkel <hfinkel at anl.gov> writes: >> Why? What is wrong with setting priorities and observing that what >> library support we already have has had a disproportional cost? > > Can you please elaborate on this disproportional cost? I think it is really important to be specific about these kinds of things for the benefit of all potential contributors. Yes. Getting the early shutdown code was way more work than it would have been if this was just a pro...
2016 Dec 13
0
LLD status update and performance chart
.... > >>> minor faults and dTLB costs). I've almost gotten to the point of > >>> implementing this just to do those measurements. > >> > >> If you do please keep it local. The bare minimum we have of > >> library > >> support is already disproportionately painful and prevents easier > >> sharing > >> with COFF. We should really not add more until the linker is done. > > > > This is so much in contrast with the LLVM development, I find it > > quite hard to see this as an acceptable position on llvm-dev. &gt...
2016 Dec 13
6
LLD status update and performance chart
...iding memory costs for input files (esp. >>> minor faults and dTLB costs). I've almost gotten to the point of >>> implementing this just to do those measurements. >> >> If you do please keep it local. The bare minimum we have of library >> support is already disproportionately painful and prevents easier sharing >> with COFF. We should really not add more until the linker is done. > > This is so much in contrast with the LLVM development, I find it quite hard to see this as an acceptable position on llvm-dev. Why? What is wrong with setting prioriti...
2016 Dec 13
0
LLD status update and performance chart
...or input files (esp. >>>> minor faults and dTLB costs). I've almost gotten to the point of >>>> implementing this just to do those measurements. >>> >>> If you do please keep it local. The bare minimum we have of library >>> support is already disproportionately painful and prevents easier sharing >>> with COFF. We should really not add more until the linker is done. >> >> This is so much in contrast with the LLVM development, I find it quite hard to see this as an acceptable position on llvm-dev. > > Why? What is wron...
2016 Dec 13
0
LLD status update and performance chart
...esday, December 13, 2016 12:09:00 PM > Subject: Re: [llvm-dev] LLD status update and performance chart > > Hal Finkel <hfinkel at anl.gov> writes: > >> Why? What is wrong with setting priorities and observing that what > >> library support we already have has had a disproportional cost? > > > > Can you please elaborate on this disproportional cost? I think it > > is really important to be specific about these kinds of things for > > the benefit of all potential contributors. > > Yes. Getting the early shutdown code was way more work than i...
2010 Jun 15
1
Skype for SIP
By the way, I am currently testing this product from Skype. I would like to be able to receive calls ona Skype name on our pbx. 1) It works beautifully and you don't have to do anything in particular. 2) It's disproportionally expensive which is why I want Skype for Asterisk to work. SfS costs $5 per month per channel just to test the beta! I find that insane, but I wanted to test it. In October, they will begin charging for Skype Manager (required for SfS) and a per seat charge for that. My guess is that the on...
2016 Dec 13
3
LLD status update and performance chart
...>>>>> minor faults and dTLB costs). I've almost gotten to the point of >>>>> implementing this just to do those measurements. >>>> >>>> If you do please keep it local. The bare minimum we have of library >>>> support is already disproportionately painful and prevents easier sharing >>>> with COFF. We should really not add more until the linker is done. >>> >>> This is so much in contrast with the LLVM development, I find it quite hard to see this as an acceptable position on llvm-dev. >> >&g...
2012 Apr 25
1
dbench & similar - as a valid benchmark
hi everybody would a tool such as dbench be a valid bechmark for gluster? and, most importantly, is there any formula to estimate raw fs to gluster performance ratio for different setups? for instance: having a replicated volume, two bricks, fuse mountpoint to volume via non-congested 1Gbps or even a volume on single brick with fuse client mountpoing locally what percentage/fraction of raw
2018 Nov 07
3
RFC: System (cache, etc.) model for LLVM
...sources pop up we can model them with different names. > > I think that's what we should do. Thank you for the detailed explanation. We could use a notion of "sustainable stream", i.e. the maximum number of (consecutive?) read/write streams that a processor can support before a disproportional loss in performance happens. This is oblivious to the reason why that performance loss happens, be it write combining buffers or prefetch streams. If there multiple such bottlenecks, it would be the minimum of such streams. At the moment I cannot think of an optimization where the difference m...
2010 May 07
2
ZFS root ARC memory usage on VxFS system...
...reasons to numerous to go into.. One thing my customers noticed immediately was a reduction in "free" memory as reported by ''top''. By way of explaining that ZFS keeps it''s cache in kernel and not in the freelist, it became apparent that memory is being used disproportionally to the filesystems. For example - On an M5000 (S10 U8) with 128 GB memory, we have 2 132GB disks in the root ZFS pool. There is no other ZFS in use on the system. We have approximately 4TB of vxfs filesystems with a very active Oracle database instance. When I do the math and count up th...
2016 Dec 13
0
LLD status update and performance chart
...gotten to the point > >>>>> of > >>>>> implementing this just to do those measurements. > >>>> > >>>> If you do please keep it local. The bare minimum we have of > >>>> library > >>>> support is already disproportionately painful and prevents > >>>> easier sharing > >>>> with COFF. We should really not add more until the linker is > >>>> done. > >>> > >>> This is so much in contrast with the LLVM development, I find it > >>> qu...
2016 Dec 13
2
LLD status update and performance chart
...>>>>> of > > >>>>> implementing this just to do those measurements. > > >>>> > > >>>> If you do please keep it local. The bare minimum we have of > > >>>> library > > >>>> support is already disproportionately painful and prevents > > >>>> easier sharing > > >>>> with COFF. We should really not add more until the linker is > > >>>> done. > > >>> > > >>> This is so much in contrast with the LLVM development, I find...
2014 Dec 19
2
[LLVMdev] [Patches][RFC] What to do about bitcode streaming.
...ented by starting lazy and calling > materializeAllPermanently. > > The thirds mode is used in tree only by llvm-dis, which means that > some bugs can hide for quite some time (222505 for example). To the > best of my knowledge it is only real user is PNaCl. > > It also has a disproportional code complexity. There are two virtual > interfaces (DataStreamer and MemoryObject) and they are leaky: Not all > bitcode features are supported when streaming and there are a few "if > (LazyStreamer)" int the reader. > > I have attached two patches that solve the pr...
2016 Dec 13
0
LLD status update and performance chart
...t strategies for avoiding memory costs for input files (esp. >> minor faults and dTLB costs). I've almost gotten to the point of >> implementing this just to do those measurements. > > If you do please keep it local. The bare minimum we have of library > support is already disproportionately painful and prevents easier sharing > with COFF. We should really not add more until the linker is done. This is so much in contrast with the LLVM development, I find it quite hard to see this as an acceptable position on llvm-dev. — Mehdio
2016 Dec 13
0
LLD status update and performance chart
...gt;>> implementing this just to do those measurements. > > > > >>>> > > > > >>>> If you do please keep it local. The bare minimum we have of > > > > >>>> library > > > > >>>> support is already disproportionately painful and prevents > > > > >>>> easier sharing > > > > >>>> with COFF. We should really not add more until the linker is > > > > >>>> done. > > > > >>> > > > > >>> This i...
2005 Apr 11
2
dealing with multicollinearity
I have a linear model y~x1+x2 of some data where the coefficient for x1 is higher than I would have expected from theory (0.7 vs 0.88) I wondered whether this would be an artifact due to x1 and x2 being correlated despite that the variance inflation factor is not too high (1.065): I used perturbation analysis to evaluate collinearity library(perturb)
2006 Jul 23
2
constructing a dataframe from a database of newspaper articles
...attempt to enhance the openness of the procedures such as the advice given by the existing psychiatrists being revealed in open court to the judge but they're aspects of streamlining rather than substantive change." He says many people are irked by a perceived disproportion between the treatment of mentally ill offenders and their victims. "As a community we need much more positively to address the situation of victims." De Jersey points to the James Bulger murder in the UK eight years ago when two 10-year-old boys abducted a...
2018 Nov 02
2
RFC: System (cache, etc.) model for LLVM
Am Do., 1. Nov. 2018 um 16:56 Uhr schrieb David Greene <dag at cray.com>: > Ok. I would like to start posting patches for review without > speculating too much on fancy/exotic things that may come later. We > shouldn't do anything that precludes extensions but I don't want to get > bogged down in a lot of details on things related to a small number of > targets.
2018 Apr 16
1
RFC: Supporting the RISC-V vector extension in LLVM
Hi, Comments below On 13 April 2018 at 16:52, Robin Kruppe <robin.kruppe at gmail.com<mailto:robin.kruppe at gmail.com>> wrote: On 13 April 2018 at 14:37, Graham Hunter <Graham.Hunter at arm.com<mailto:Graham.Hunter at arm.com>> wrote: Hi, Nice to see another group tackling length agnostic vectorization :) I'm still reading through all the details, but I do have one