mirror of
https://gitlab.freedesktop.org/cairo/cairo.git
synced 2026-01-20 20:40:25 +01:00
411c09eed7
Real applications that control their Drawable externally to Cairo are 'disadvantaged' by cairo-perf-trace when it creates a similar surface for each new instance of the same Drawable. The difficulty in maintaining one perf surface for every application surface is that the traces do not track lifetimes for the application surfaces, so we would just accumulate stale surfaces. The surface cache takes a different approach and returns the same surface for each active Drawable, and maintains a hold-over of the MRU 16 surfaces. This achieves 60-80% hit rate with firefox, which is probably as good as can be expected. Obviously for double-buffered applications we only every draw to freshly created surfaces (and Gtk+ bypasses cairo to do the final copy -- the ideal application would just use a push-group for double buffering, in which case we would capture and replay the entire expose event). To enable use of the surface cache whilst replaying use -c: ./cairo-perf-trace -c firefox-talos-gfx |
||
|---|---|---|
| .. | ||
| examples | ||
| .gitignore | ||
| cairo-script-file.c | ||
| cairo-script-hash.c | ||
| cairo-script-interpreter.c | ||
| cairo-script-interpreter.h | ||
| cairo-script-objects.c | ||
| cairo-script-operators.c | ||
| cairo-script-private.h | ||
| cairo-script-scanner.c | ||
| cairo-script-stack.c | ||
| COPYING | ||
| csi-bind.c | ||
| csi-exec.c | ||
| csi-replay.c | ||
| csi-trace.c | ||
| Makefile.am | ||