Previously the majority of the VM was under a single token, the vm_token; now vm_objects (mappable entities) are each under a private token, concurrent page faults in the same object can proceed, and VM SMP scalability overall improved. Results for Postgres and MySQL, among others, are excellent.
-Francois Tigeot [worked on benchmarks](http://leaf.dragonflybsd.org/mailarchive/kernel/2011-11/msg00004.html) comparing DragonFly 2.10 and DragonFly 2.13, among other operating systems. The [resulting graphs](http://dl.wolfpond.org/Pg-benchmarks.dfly_only.pdf) show how well DragonFly responds to multiple CPUs. (2.13 is the version of DragonFly that became 3.0.)
+Francois Tigeot [worked on benchmarks](http://leaf.dragonflybsd.org/mailarchive/kernel/2011-11/msg00004.html) comparing DragonFly 2.10 and DragonFly 2.13, among other operating systems. The [resulting graphs](http://dl.wolfpond.org/Pg-benchmarks.dfly_only.pdf) show how well DragonFly responds to multiple CPUs. (2.13 is the development version of DragonFly that became 3.0.)
See: