| commit | d9ebcfc2d9fb9c4312a4ebbb64ce66e1484df53c | |
| author | Waleed Khan <[email protected]> | |
| Fri, 12 Jun 2020 23:10:28 +0000 (12 16:10 -0700) | ||
| committer | Facebook GitHub Bot <[email protected]> | |
| Fri, 12 Jun 2020 23:13:11 +0000 (12 16:13 -0700) | ||
| tree | 62b27e5a27042f27eba6f9ba427b64a5a4a419d7 | treesnapshot (tar.gz zip) |
| parent | 93a3fa6e5f469365bb0b08445fda25d884d5080b | commitdiff |
Cache prepared statements in `Naming_sqlite`
Summary: Currently, `Naming_sqlite` creates and finalizes prepared statements. This means that we have to incur the overhead of parsing/compiling the prepared statement on each query. We can save time by reusing the prepared statements instead.
Reviewed By: 2BitSalute
Differential Revision: D22025396
fbshipit-source-id: 8a36ffd6e2f92225d2549ce4e2eef0e8ef8c4c61
Summary: Currently, `Naming_sqlite` creates and finalizes prepared statements. This means that we have to incur the overhead of parsing/compiling the prepared statement on each query. We can save time by reusing the prepared statements instead.
Reviewed By: 2BitSalute
Differential Revision: D22025396
fbshipit-source-id: 8a36ffd6e2f92225d2549ce4e2eef0e8ef8c4c61
| hphp/hack/src/naming/naming_sqlite.ml | diffblobblamehistory |