Indeed. This is for my base SQLite3 3.30.0 x64 with the same configuration as the prior x64 stats. Note how much more memory it takes and how much slower it is. ``` SQLite version 3.30.0 2019-10-04 17:51:20 Enter ".help" for usage hints. Connected to a transient in-memory database. Use ".open FILENAME" to reopen on a persistent database. sqlite> .mode list sqlite> .stats on sqlite> .timer on sqlite> .open test.db sqlite> select * from tripsummary; [ ... output elided ...] Memory Used: 39516528 (max 3174130272) bytes Number of Outstanding Allocations: 200668 (max 598267) Number of Pcache Overflow Bytes: 422664 (max 1663026784) bytes Largest Allocation: 19398656 bytes Largest Pcache Allocation: 4360 bytes Lookaside Slots Used: 100 (max 100) Successful lookaside attempts: 450 Lookaside failures due to size: 5394 Lookaside failures due to OOM: 1168975 Pager Heap Usage: 421864 bytes Page cache hits: 11974 Page cache misses: 96 Page cache writes: 0 Page cache spills: 0 Schema Heap Usage: 432616 bytes Statement Heap/Lookaside Usage: 37869344 bytes Fullscan Steps: 622088 Sort Operations: 502 Autoindex Inserts: 1320 Virtual Machine Steps: 1127164121 Reprepare operations: 0 Number of times run: 1 Memory used by prepared stmt: 37869344 Run Time: real 26.297 user 25.156250 sys 1.015625 sqlite> ``` So that is 3027 MB which would run in x64 or x86 with Large Address Aware (on x64) or x86 with Large Address Aware and /3GB enabled, but would not run in a standard windows x32 2GB process.