> why, when you've got 16 GB ram, does a 6.4 GB vector cause any problems?
Architecturally, 4 GB is like the sound barrier -- you may get turbulence or a sonic boom. Because 4 GB was the limit for 32 bit word size any residual 32 bit code or 32 bit assumptions anywhere in the stack (or CPU) could create issues. The operating system attempts to present a unified linear address space, but under the hood all sorts of kludges may exist. Windows AWE exists because of 4 GB. https://en.wikipedia.org/wiki/Address_Windowing_Extensions Thus, from an architectural standpoint, I would try to avoid allocating 4 GB of RAM to one object under ANY operating system, but if I had to do it I would try Linux because that is what the supercomputers use (supercomputers have big memory in addition to fast speed and tens of thousands of cpus). https://www.zdnet.com/article/linux-totally-dominates-supercomputers/ Twenty-five years ago developers were more concerned about Y2K, than beyond 4 GB. To the extent anyone in the Windows NT world thought about 4 GB of RAM, it was allocating memory between the operating system and applications WITHIN 4 GB (ie. do we split 4 GB of RAM between opsys:apps 2:2 or 1:3). Jim Callahan Orlando, FL On Mon, May 28, 2018 at 5:35 AM, Rowan Worth <row...@dug.com> wrote: > On 28 May 2018 at 17:29, x <tam118...@hotmail.com> wrote: > > > I’ve just discovered the thread in the original app decreases the > > available memory by around 4 GB. Are they really that expensive? > > > A thread itself is not expensive in terms of memory. > > > > It has very little data of its own > > > Either this statement is wrong, or you've misattributed the 4 GB of memory. > -Rowan > _______________________________________________ > sqlite-users mailing list > sqlite-users@mailinglists.sqlite.org > http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users > _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
