X11PERF DOWNLOAD

Rectangle size 10x10 x x NoAccel And that gives me an excuse to put in a performance plot:. So there's some room for improvement there, ExaOffscreenMarkUsed is at the top of the profile, and as I've mentioned before it looks ripe for improvement. Meanwhile XAA scored 4. I'm told that the long-awaited memory management work, TTM , is what will solve this. Meanwhile, it's fairly silly that there's a bunch of memcpy operations to migrate things from "system" to "video" memory on the i anyway. I think the answer is no on both points.

Uploader:	Zuluktilar
Date Added:	18 February 2007
File Size:	17.8 Mb
Operating Systems:	Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/X
Downloads:	71870
Price:	Free* [*Free Regsitration Required]

- x11perf Test Profile

x11pref So let me clear things up now: There are some exceptions such as the trender utility for mozilla and special command-line options for the swfdec player. Some things are plainly working well, such as the fact that the pixman time has gone down.

When going from the non-few to the "few" variants, both Glucose and EXA slow down significantly. So there are likely easy ways to improve x11perrf as well. If you see someone benchmarking with only toys like x11perf or gtkperf, go ahead and point them to this post, or the the cairo-perf-trace entry in the cairo FAQ, and insist on benchmarks from real applications.

On 2D Performance Measurement Trying to get a handle on 2D graphics rendering x11lerf can be a difficult task. Such benchmarks usually measure drawing speed for lines, polygons, text, etc.

performance

X1p1erf so the driver was waiting for each composite operation to finish before reusing the buffer. Recall that in January Eric and I had been disappointed to report that even after a recent 2x improvement, the intel-batchbuffer branch was only atglyphs per second compared tofor XAA.

The obvious fix I implemented is to simply malloc a buffer, do the rasterization, and only then copy the result to a pixmap. So a very simple patch eliminates the software fallback.

If you click through to my blog, you'll get to see these charts in their colorful glory. Posted Thu 27 Sep Time lost migrating pixmaps with memcpy Time wasted while x11pegf driver busy-waited between operations Here's a run-down of what I could find about progress on solving these two problems: While it can be used as a benchmark, it was written and is intended as a performance testing tool.

FreshPorts -- x11/x11perf: X11 server performance test program

We consider such numbers to be uninformative at best and misleading at worst. Again, click through to my blog if you're just getting a list of numbers, not a colorful bar chart.

It's also nice that evas includes many backends which can be interesting for comparison. So, briefly here, I want to mention a couple of things that EXA is doing a fine job with. I've followed those instructions and run a benchmark comparing Glucose and EXA. The first is the big reason why you don't want to run an X server with NoAccel: Instead, the most important thing I feel I could do for cairo now is to continue to improve X 2D performance.

I hope to have something worth sharing soon. There's really a very welcoming community of very intelligent people around the X server who are glad to help guide new people who want to help. A much more interesting experiment allows us to start exploring where will be able to get with some un-broken hardware acceleration. It makes it easy to run a one-off Trender loop for hundreds of iterations so I can profile exactly the rendering and nothing else. Running your server with NoAccel is not a good idea EXA does accelerate a lot of things already EXA is not doomed, nor were its authors idiots to have written it The reason my posts have focused on negative performance aspects is because I was looking for things that could be sped up, and as is only appropriate I looked for, found, and have been focused on the biggest performance problem with EXA I could find, which turns out to be glyph rendering.

Introducing cairo-perf-trace Over the past year or so, Chris "ickle" Wilson has been putting a lot of work into a debugging utility known as cairo-trace, inspired by work on an earlier tool known as libcairowrap by Benjamin Otte and Jeff Muizelaar. Posted Tue 15 Jul I might still not have everything compiled or running correctly yet, but I'm quite sure that at least some Glucose code was active during my Glucose run.

Anyway, Richard totally rocks for having put this together. Unsourced material may be challenged and removed. Use specified raster ops default is GXcopy. Please help improve this article by adding citations to reliable sources. I asked Keith Packard about why these glyph images are being pinned to system memory, and he explained that what was preventing the glyphs from migrating is that the X server has not been using straight Pixmaps for glyphs, but something slightly different.