similar to: [LLVMdev] New inliner metrics

Hello all, Finally find some time to get back to the NHW Project.I was thinking about making a technology demo, and I wanted to highlight the uniqueness of the NHW codec that is neatness/sharpness preserving or enhancement.With my eyes, I can see that the NHW codec has more neatness/sharpness than the other codecs (x265, x264, WebP, Rududu, JPEG,...), but for a demo there must be objective

Xinliang David Li wrote: > Hi, I browsed the LLVM inliner implementation, and it seems there is > room for improvement. (I have not read it too carefully, so correct me > if what I observed is wrong). > > First the good side of the inliner -- the function level summary and > inline cost estimation is more elaborate and complete than gcc. For > instance, it considers callsite

I've managed to trap the following segfault with xxgdb and gctorture() set. The segfault seems to move around if gctorture() is not set, but has now occurred twice in the same spot with it set. xxgdb gives the message Program received signal SIGSEGV, Segmentation fault. 0x71244 in RunGenCollect (size_needed=2) at memory.c:1027 and the source listing points to FORWARD_CHILDREN(s); in the

On Tue, Nov 23, 2010 at 8:07 PM, Xinliang David Li <xinliangli at gmail.com> wrote: > Hi, I browsed the LLVM inliner implementation, and it seems there is room > for improvement.  (I have not read it too carefully, so correct me if what I > observed is wrong). > First the good side of the inliner -- the function level summary and inline > cost estimation is more elaborate and

On Jun 24, 2013, at 3:09 PM, Chandler Carruth <chandlerc at gmail.com> wrote: On Mon, Jun 24, 2013 at 2:59 PM, Nadav Rotem <nrotem at apple.com> wrote: > I agree. The vectorizer is a *lowering* pass, and much like LSR and it loses information. A few months ago some of us talked about this and came up with a general draft for the ideal pass ordering. > > Where? On the

On Wed, Nov 24, 2010 at 12:37 PM, Nick Lewycky <nicholas at mxc.ca> wrote: > Xinliang David Li wrote: > >> Hi, I browsed the LLVM inliner implementation, and it seems there is >> room for improvement. (I have not read it too carefully, so correct me >> if what I observed is wrong). >> >> First the good side of the inliner -- the function level summary

Last month, we started publicly posting monthly community metrics reports with all kinds of interesting information about the Puppet Community. I also realized that I did a couple of blog posts about this, but I had not posted it here on the mailing list for your reading pleasure. The latest version of the metrics can be found here: http://puppetlabs.com/community/metrics/ Here is a quick summary

I need to calculate some metrics such as Mean Time Between Failure (MTBF), etc (see http://www.cs.sandia.gov/~jrstear/ras for a more complete list). I have observations like start end state 1 2005-11-11 09:05:00 2005-11-11 12:20:00 Scheduled Downtime 2 2005-11-12 13:42:00 2005-11-12 14:45:00 Unscheduled Downtime where each row describes

On Nov 23, 2010, at 5:07 PM, Xinliang David Li wrote: > Hi, I browsed the LLVM inliner implementation, and it seems there is room for improvement. (I have not read it too carefully, so correct me if what I observed is wrong). > > First the good side of the inliner -- the function level summary and inline cost estimation is more elaborate and complete than gcc. For instance, it considers

Hi, How much do you care about call quality metrics to collect and analyze them? What metrics are of interest for you (of course packet loss, jitter, latency, but what else?). We have collected some for your review and would be happy to expand them with those you are using in your Asterisk systems. http://blog.sevana.fi/recommended-voip-call-quality-metrics/ Best Regards, Sevana

Hello Is it able to obtain performance metrics from puppet master ( or puppet dashboard ) ? I intend to use this metrics in external monitoring system. Of particular interest are the following metrics: * list of agents * time since the certain agent last apply manifest ( to find stuck agents ) * time used to compile manifest by puppet master for the certain agent * time used by the certain

Hi All Newbie to wine here :) I have installed wine, and can get notepad and winemine up, but when I do, I get a painfully long list of messages and then it goes into Font Metrics 1.1% - Font Metrics 1.2% untill we eventually get to 100%. I also tried to run File Maker Pro 5 for windows, however the window opened and just hung for about 15 mins before I killed the process. I have checked the

> On May 12, 2016, at 11:21 PM, Elena Lepilkina via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > Hi all, > > As we understood great changes will be done in LNT, so we are waiting to new LNT version and stopped our work in LNT. > > One more question about using test-suite separately with cmake. Cmake can only build all tests and generate lit tests. After that we

Hi, When I ran wine for the first time, font metrics information is built. It doesn't take a lot of time, but when you are forwarding X session over half a world, this can be pretty slow and annoying. Well, I know that there is probably no way how to avoid this, but I think there is a way how to avoid this when you reinstall wine. So, question is, where is stored font metrics information

Hi, I am attempting to write a monitor to gather Samba Server performance metrics. I would like to get raw metrics directly from the server itself rather than a 3rd party tool. Could anyone point me to docs or enlighten me on how to accomplish this? I am looking to determine the availability of the server (up or down), the number of files requested, any caching information available

> On May 26, 2016, at 7:08 AM, Elena Lepilkina via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > I understood your modules and I see as them can be used in LNT. But there are some question about old features. > 1. With Makefiles we can write pass and collect some statistics. There was an example of branch pass. Metrics can be collected by > @-$(LOPT) -load

Hello, I have a machine with suse10.1 with the xen pae kernel installed. The machine has 6GB of memory, 150GB hd and a 2nd 300GB hd to store xen images. I run 2 xen images on the machines each with 2.5GB and Dom0 with 300MB. For some reason the images have been very slow, I use these images to install my company''s installers and they hang sometimes which does not happen on native

Hello guys, as you probably have already understood, I'm trying to make asterisk realtime work. Well, now it's working, but I'm not fully understanding the "metrics". In voip-info.org I found that they are a sort of "position" inside a context (var_metric) or the index of the context (cat_metric). Am I right? Where can I obtain more info about these

Hi! metrics.dovecot.org will be removed by end of April. It's not really used that much and it's not compatible with new style metrics. --- Aki Tuomi Open-Xchange oy

Hi Elena, > First of all, now LNT uses make-style of running tests and parse results from result csv file. Are there any plans to go to cmake? There are two test drivers in LNT. "lnt runtests nt" uses the old Makefile-based system and "lnt runtests test-suite" uses the new cmake-based system. It sounds like you are using the former and should switch to the latter.