Re: [w3c/IndexedDB] Allow more explicit control over transaction lifetimes (#34)

evanstade left a comment (w3c/IndexedDB#34)

By the way, the lack of ability to disable autocommit is a performance bug since working around it requires intense polling. See [Dexie.waitFor()](https://dexie.org/docs/Dexie/Dexie.waitFor()):

> WARNING: This method can be CPU intensive while waiting for given Promise. It typically triggers about 1000 dummy-queries while waiting for just a 100 milliseconds.
Use with caution when the purpose is to keep a transaction alive as it may put unnecessary CPU load on the browser. A separate task will keep the transaction alive by propagating dummy-requests on the transaction while the given promise is being executed.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3c/IndexedDB/issues/34#issuecomment-5415607146
You are receiving this because you are subscribed to this thread.

Message ID: <w3c/IndexedDB/issues/34/5415607146@github.com>