Op 9 jan 2014, om 19:50 heeft Ward Willats het volgende geschreven:
BUT, I was wondering if there are scenarios where only two threads
can bounce each other into busy sleep like two bocci balls colliding?
(one thread wanted a read lock, the other a BEGIN EXCLUSIVE write lock)
On Jan 9,
On Jan 9, 2014, at 10:10 AM, Roger Binns wrote:
> The default busy handler (see sqliteDefaultBusyCallback in source) sleeps
> for these amount of milliseconds:
>
> { 1, 2, 5, 10, 15, 20, 25, 25, 25, 50, 50, 100 };
>
> However on non-Windows if you do not have
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 09/01/14 08:53, Ward Willats wrote:
> I found the UI thread and a worker thread, both in the DB, both in the
> default busy handler, both taking a 1 second sleep.
>
> I expected to see a third thread in the DB doing some work while the
> other two
I've got a multi-threaded iOS app. Each thread has its own long-lived DB
connection.
I was debugging a "stuttering" in the UI thread and broke into the debugger
during one of the pauses.
I found the UI thread and a worker thread, both in the DB, both in the default
busy handler, both taking a
4 matches
Mail list logo