doubled speed with esqeleto
This commit is contained in:
parent
80c8ebbf98
commit
69a1aaa40f
1 changed files with 7 additions and 0 deletions
|
@ -18,6 +18,9 @@ generated and updated by looking at the git repository.
|
||||||
"regenerated" by running fsck again.
|
"regenerated" by running fsck again.
|
||||||
(Perhaps doesn't quite fit, but let it slide..)
|
(Perhaps doesn't quite fit, but let it slide..)
|
||||||
|
|
||||||
|
Store in the database the Ref of the branch that was used to construct it.
|
||||||
|
(Update in same transaction as cached data.)
|
||||||
|
|
||||||
## case study: persistent with sqllite
|
## case study: persistent with sqllite
|
||||||
|
|
||||||
Here's a non-normalized database schema in persistent's syntax.
|
Here's a non-normalized database schema in persistent's syntax.
|
||||||
|
@ -93,6 +96,10 @@ With this, 1000 queries takes 0.406s. Note that persistent is probably not
|
||||||
actually doing a join at the SQL level, so this could be sped up using
|
actually doing a join at the SQL level, so this could be sped up using
|
||||||
eg, esquelito.
|
eg, esquelito.
|
||||||
|
|
||||||
|
Update2: Using esquelito to do a join got this down to 0.250s.
|
||||||
|
|
||||||
|
Code: <http://lpaste.net/101141> <http://lpaste.net/101142>
|
||||||
|
|
||||||
Compare the above with 1000 calls to `associatedFiles`, which is approximately
|
Compare the above with 1000 calls to `associatedFiles`, which is approximately
|
||||||
as fast as just opening and reading 1000 files, so will take well under
|
as fast as just opening and reading 1000 files, so will take well under
|
||||||
0.05s with a **cold** cache.
|
0.05s with a **cold** cache.
|
||||||
|
|
Loading…
Add table
Add a link
Reference in a new issue