We can bypass a lot of synchronous read operations in nsINavBookmarkService by directly using SQL. These will be async where available and often even simpler to use than Places' query API. (Maybe not on 3.5/3.6 where we need to make JOINs to get GUIDs.)

\o/

This is likely true, but makes me sad. Monkeypatching ftl!

(In reply to comment #2) > This is likely true, but makes me sad. Monkeypatching ftl! No monkey patching needed... Just stop using the APIs in nsINavBookmarkService and run queries against its DBConnection instead. We already do that in *some* parts of the bookmark engine (cf bug 615410, bug 623418), just not in all. Going fwd we could even use a separate read-only db connection to avoid lock contention with simultaneous write operations.

Marco, assigning it to you to reprioritize this for snappy purposes or wontfix.

Marco says P2 is correct. < mak> taras: I discussed that with rnewman already, I think Sync team may have resources in January rnewman can reassign this in his team

See also Bug 519514, which might be a better approach.