using other words:
does the one-write-lock-per-database policy (it's not a "bug" but a "feature" by design) affect contention making its usage in certain kind of workloads less then optimal?
if not how do you maintain that kind of workload?
would you use an async-write-queue at the application level? (roll-backing would be difficult with such a structure though)