From: sqlite-users-boun...@sqlite.org [sqlite-users-boun...@sqlite.org] on
behalf of Udi Karni [uka...@gmail.com]
Sent: Saturday, March 24, 2012 3:48 PM
To: General Discussion of SQLite Database
Subject: EXT :Re: [sqlite] 64-bit Windows Command Shell
I tried the SQLite
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 25/03/12 08:44, Jay A. Kreibich wrote:
> No, there wasn't. I'm saying the OS shouldn't cache blocks from
> filesystems that reside on a ramdisk volume.
We were talking at cross purposes. I was talking about the OPs issue and
moving a database
On Sat, Mar 24, 2012 at 09:53:47PM -0700, Roger Binns scratched on the wall:
> Yes, but the tools primarily come from the OS vendor. After all they have
> to be able to compile and debug the code making up the operating system
> and base applications.
Which makes it all the more
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 24/03/12 20:14, Jay A. Kreibich wrote:
> Not to nit-pick, but an OS doesn't make it, or not make it, difficult
> to compile something. That's usually due to crappy tools and poor
> support.
Yes, but the tools primarily come from the OS vendor.
On Sat, Mar 24, 2012 at 06:56:16PM -0700, Roger Binns scratched on the wall:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 24/03/12 18:23, Jay A. Kreibich wrote:
> > That depends on the OS. Some 64-bit OSes will give nearly all the 4GB
> > address space to a 32-bit application.
>
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 24/03/12 18:23, Jay A. Kreibich wrote:
> That depends on the OS. Some 64-bit OSes will give nearly all the 4GB
> address space to a 32-bit application.
Those same OSes make it very easy to compile SQLite in 64 bits so this
isn't an issue.
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 24/03/12 18:16, Udi Karni wrote:
> (1) On the SQLite Download page - the Linux version just says "x86"
> while the Windows version is "Win-32 x86". Does this mean that the
> Linux version is a 64-bit version? In other words - if run on, say,
>
On 25 Mar 2012, at 2:16am, Udi Karni wrote:
> (2) On Windows - a RamDisk "drive letter" can be used beneficially in 2
> ways -
> (a) to contain the database itself
> (b) to serve as a destination for the TEMP and TMP - which SQLite (through
> Windows I suppose) uses often as a
On Sat, Mar 24, 2012 at 05:36:09PM -0700, Roger Binns scratched on the wall:
> > In my particular scenario - while the raw data being attached and read
> > is hundreds of GB - the result sets are only a few GB.
>
> 2GB is the threshold to switch to 64 bits.
That depends on the OS. Some
Very interesting. 2 questions -
(1) On the SQLite Download page - the Linux version just says "x86" while
the Windows version is "Win-32 x86". Does this mean that the Linux version
is a 64-bit version? In other words - if run on, say, RedHat 5.5 64-bit -
it will be able to use >4GB of RAM?
(2)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 24/03/12 13:48, Udi Karni wrote:
> I tried the SQLite in-memory DB feature - but when it exceeded about
> 2GB - I got the "out of memory" message.
Technically it ran out of address space, not ram.
> In my particular scenario - while the raw data
I tried the SQLite in-memory DB feature - but when it exceeded about 2GB -
I got the "out of memory" message.
In my particular scenario - while the raw data being attached and read is
hundreds of GB - the result sets are only a few GB.
A 64-bit version of SQLite that could handle an in-memory DB
There is a natural 5th extrapolation:
5) Could sqlite3 take advantage of multiple cpu's by parsing a single task
into one thread per cpu and segment data to be worked by each thread? Big
league stuff. But I don't think sqlite3 is meant to compete in that
market. It already exceeds expectations
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 21/03/12 16:57, Udi Karni wrote:
> Frankly I don't know if a 64-bit version and Big RAM would make a
> difference and if so - up to what point.
A 64 bit Windows command shell won't wave a magic wand. In any event you
can compile one yourself and
Frankly I don't know if a 64-bit version and Big RAM would make a
difference and if so - up to what point. With SQLite being a single process
- assigned for the most part to a single CPU - even if everything was done
in RAM - there is a limit to what 1 CPU can do.
I am just noticing anecdotally
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 21/03/12 11:09, Black, Michael (IS) wrote:
> Cache is the primary (and obvious) thing I can think of.
With a 32 bit compilation you'll be able to bump it up to about 2GB.
However by that point you will long have passed diminishing returns and
can
...@sqlite.org] on
behalf of Roger Binns [rog...@rogerbinns.com]
Sent: Wednesday, March 21, 2012 12:57 PM
To: General Discussion of SQLite Database
Subject: EXT :Re: [sqlite] 64-bit Windows Command Shell
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 21/03/12 05:28, Udi Karni wrote
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 21/03/12 05:28, Udi Karni wrote:
> Is there - or can we kindly request that a 64-bit version of the
> Command Shell be offered on the download page?
>
> A version that could run on Windows 7 64-bit and effectively use large
> RAM?
Which bit of
Hello,
Is there - or can we kindly request that a 64-bit version of the Command
Shell be offered on the download page?
A version that could run on Windows 7 64-bit and effectively use large RAM?
Thanks !
___
sqlite-users mailing list
19 matches
Mail list logo