On Sun, Apr 11, 2010 at 2:40 AM, Avi Kivity <avi@xxxxxxxxxx> wrote: > On 04/11/2010 12:37 PM, Jason Garrett-Glaser wrote: >> >>> # time x264 --crf 20 --quiet crowd_run_2160p.y4m -o /dev/null --threads 2 >>> yuv4mpeg: 3840x2160@50/1fps, 1:1 >>> >>> encoded 500 frames, 0.68 fps, 251812.80 kb/s >>> >>> real 12m17.154s >>> user 20m39.151s >>> sys 0m11.727s >>> >>> # echo never> /sys/kernel/mm/transparent_hugepage/enabled >>> # echo never> /sys/kernel/mm/transparent_hugepage/khugepaged/enabled >>> # time x264 --crf 20 --quiet crowd_run_2160p.y4m -o /dev/null --threads 2 >>> yuv4mpeg: 3840x2160@50/1fps, 1:1 >>> >>> encoded 500 frames, 0.66 fps, 251812.80 kb/s >>> >>> real 12m37.962s >>> user 21m13.506s >>> sys 0m11.696s >>> >>> Just 2.7%, even though the working set was much larger. >>> >> >> Did you make sure to check your stddev on those? >> > > I'm doing another run to look at variability. > >> I'm also curious how it compares for --preset ultrafast and so forth. >> > > Is this something realistic or just a benchmark thing? Well, at 2160p, we're already a bit beyond the bounds of ordinary applications. Ultrafast is generally an "unrealistically fast" setting, getting stupid performance levels like 200fps 1080p encoding (at the cost of incredibly bad compression). "veryfast" is probably a more realistic test case (I know many companies using similar levels of performance). Jason -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@xxxxxxxxxx For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: <a href