--- mos <[EMAIL PROTECTED]> wrote:
> At 01:42 PM 8/9/2007, you wrote:
> >--- mos <[EMAIL PROTECTED]> wrote:
> > > Is there no way to allocate more memory to SQLite index buffers like you
> > > can with MySQL and most other databases? I suspect SQLite is building the
> > > index on disk which will b
> Anyone know a simple Windows command line equivalent
> of the cat to dev null command above to put a file
> into OS cache?
The command would be:
type filename.db > nul
but I'm pretty sure that this does not work the same
way under Windows as it does in *Nix.
__
At 01:42 PM 8/9/2007, you wrote:
--- mos <[EMAIL PROTECTED]> wrote:
> Is there no way to allocate more memory to SQLite index buffers like you
> can with MySQL and most other databases? I suspect SQLite is building the
> index on disk which will be 100x slower than if it used RAM. The indexing
>
--- mos <[EMAIL PROTECTED]> wrote:
> Is there no way to allocate more memory to SQLite index buffers like you
> can with MySQL and most other databases? I suspect SQLite is building the
> index on disk which will be 100x slower than if it used RAM. The indexing
> process has used 400MB of RAM so
At 12:10 PM 8/9/2007, you wrote:
> > > cat your.db > /dev/null
>
> >
> > Using Windows XP. :-0
>
> Anyone know a simple Windows command line equivalent of the cat
> to dev null command above to put a file into OS cache?
Well, 'type your.db > nul' will do the same thing, though whether or not
> > > cat your.db > /dev/null
>
> >
> > Using Windows XP. :-0
>
> Anyone know a simple Windows command line equivalent of the cat
> to dev null command above to put a file into OS cache?
Well, 'type your.db > nul' will do the same thing, though whether or not it
will remain in the cache is
Regarding:
> > cat your.db > /dev/null
>
> Using Windows XP. :-0
---
>Anyone know a simple Windows command line equivalent of the cat to dev
null command above to put a file into OS cache?
>You could write a small C program to do this, I suppose.
=
--- mos <[EMAIL PROTECTED]> wrote:
> At 10:19 AM 8/9/2007, you wrote:
> >If your database file is less than the size of your RAM,
> >then do this before the create index to speed it up:
> >
> > cat your.db > /dev/null
>
> Using Windows XP. :-0
Anyone know a simple Windows command line equival
At 10:19 AM 8/9/2007, you wrote:
If your database file is less than the size of your RAM,
then do this before the create index to speed it up:
cat your.db > /dev/null
See also:
PRAGMA cache_size = number-of-pages;
and
PRAGMA page_size = bytes; -- recommend at least 8192
http://www.sql
If your database file is less than the size of your RAM,
then do this before the create index to speed it up:
cat your.db > /dev/null
See also:
PRAGMA cache_size = number-of-pages;
and
PRAGMA page_size = bytes; -- recommend at least 8192
http://www.sqlite.org/pragma.html
--- mos <[EMA
Hi Mike,
i have noticed that things take a lot longer if they aren't surrounded by a
BEGIN;
do work;
COMMIT;
does that make a difference for you?
Paul
On 09/08/07, mos <[EMAIL PROTECTED]> wrote:
> I'm building my first index on a large table using the "Create index
> ix_Main on Table1(StringFie
I'm building my first index on a large table using the "Create index
ix_Main on Table1(StringField1,StringField2,DateField,TimeField)" and so
far it has been running over an hour on a fast computer with 2gb ram. There
are 15 million rows in the table. The same index can be built in MySQL in a
m
12 matches
Mail list logo
