Overview
Comment: | Added notes for in-memory db for speed up |
---|---|
Downloads: | Tarball | ZIP archive | SQL archive |
Timelines: | family | ancestors | descendants | both | trunk |
Files: | files | file ages | folders |
SHA1: |
6f83bffb0daeb3bf259df840c3d9cfc9 |
User & Date: | matt on 2013-11-09 05:45:54 |
Other Links: | manifest | tags |
Context
2013-11-09
| ||
23:01 | Inmemdb support mostly done. Syncing runs and test_meta table not yet done. check-in: 592afa20f6 user: matt tags: trunk | |
13:55 | Starting v1.60 series check-in: f172579176 user: matt tags: v1.60, v1.6001 | |
05:45 | Added notes for in-memory db for speed up check-in: 6f83bffb0d user: matt tags: trunk | |
05:10 | Merged v1.55 to trunk check-in: 9da006893d user: matt tags: trunk | |
Changes
Modified NOTES from [f5959ca38f] to [bd55d51ed2].
1 2 3 4 5 6 7 | [87cbe68f31] [be405e8e2e] # FROM andyjpg on #chicken (let ((original-exit (exit-handler))) | > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > | 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 | ====================================================================== Try writing to in-memory db and every 2-5 seconds syncing to megatest.db ====================================================================== First, how much time will it take to write back the changes: 1. Get the run table (define (get-all db)(let ((res '()))(for-each-row (lambda (a . b)(set! res (cons (apply vector a b) res))) db "SELECT * FROM tests;") res)) (define tdata (let ((start (current-milliseconds))(res (get-all *db*)))(print (- (current-milliseconds) start))res)) Result ranges from 34ms to 89ms but mostly around 40ms for 623 records on moosefs Projecting to 15000 records: Slow 2 seconds to read all Median 1 second to read all This seems like it would work with an update period of 2-5 seconds TODO ---- 1. open-db opens in-memory db and megatest.db, put handles in *memdb* and *db*, *memdb* is < run-id dbh > 2. Server is part of runtests a. server start cycle - adapt to per run-id i. states; starting, started, stopping, stopped b. turn off write coalesing 3. Calls to -runtests, -remove-runs etc. a. Might talk to running server if run specific b. Can talk to megatest.db but not a generally good idea c. Can start a runserver 4. Dashboard is fine except for writes? ====================================================================== [87cbe68f31] [be405e8e2e] # FROM andyjpg on #chicken (let ((original-exit (exit-handler))) |
︙ | ︙ |