Closed GoogleCodeExporter closed 9 years ago
Thank you for your report.
What about adding sqlite3_busy_timeout directly into DbConn::GetDb() method?
Also I think one second can be too small delay in case of server under heavy
loading.
Original comment by loentar
on 3 Oct 2012 at 6:29
[deleted comment]
Yes I didn't see it but you can add sqlite3_busy_timeout directly into
DbConn::GetDb() method.
Concerning the delay I don't know what could be the best value. Few seconds
seems ok. I think it should be interesting to have this value as an environment
variable like STAFF_LOG_LEVEL, STAFF_LOG_FILE...
Original comment by julien.d...@gmail.com
on 4 Oct 2012 at 5:56
I've made some tests with sqlite3_busy_timeout = 5000 into DbConn::GetDb()
method.
Everything works better.
I have no error even if I use
StartServers 5
MinSpareServers 5
MaxSpareServers 5
(20% error at the beginning with only sqlite3_busy_timeout == 1000)
Today the results are:
Users ; Req/user ; Total ; %Errors ;
20 ; 3000 ; 60000 ; 0% ; from 190 to 200 req/sec
Min: 8 ms
Max: 2158 ms
Original comment by julien.d...@gmail.com
on 4 Oct 2012 at 12:31
you can use now STAFF_SQLITE_BUSY_TIMEOUT environment variable to set value of
sqlite3_busy_timeout().
Original comment by loentar
on 4 Oct 2012 at 6:49
This issue was closed by revision r714.
Original comment by loentar
on 4 Oct 2012 at 6:49
Original issue reported on code.google.com by
julien.d...@gmail.com
on 3 Oct 2012 at 11:08