On the different note, I am having about 1000 connection to the same SQLite
data and as expected, it will be slower. What would be an efficient way to
make it fast? I am opening dataset as Read Only.
Thanks
Gaurav
On Fri, Nov 25, 2011 at 4:52 PM, Jay A. Kreibich wrote:
> On Thu, Nov 24, 2011 a
On Thu, Nov 24, 2011 at 05:22:38PM +, Simon Slavin scratched on the wall:
> On 24 Nov 2011, at 5:10pm, Jay A. Kreibich wrote:
> > On Thu, Nov 24, 2011 at 08:08:12AM +, Simon Slavin scratched on the
> > wall:
> >
> >> It is faster to search integers than it is to search real numbers.
> >
It works!!
Thanks a lot Simon!
Gaurav
On Thu, Nov 24, 2011 at 11:22 AM, Simon Slavin wrote:
>
> On 24 Nov 2011, at 5:10pm, Jay A. Kreibich wrote:
>
> > On Thu, Nov 24, 2011 at 08:08:12AM +, Simon Slavin scratched on the
> wall:
> >
> >> It is faster to search integers than it is to search
On 24 Nov 2011, at 5:10pm, Jay A. Kreibich wrote:
> On Thu, Nov 24, 2011 at 08:08:12AM +, Simon Slavin scratched on the wall:
>
>> It is faster to search integers than it is to search real numbers.
>
> Why? Both types are a string of 64 bits. Both types use the same
> integer-based log
On Thu, Nov 24, 2011 at 08:08:12AM +, Simon Slavin scratched on the wall:
> It is faster to search integers than it is to search real numbers.
Why? Both types are a string of 64 bits. Both types use the same
integer-based logic for the =, <, and > operations.
The only real differenc
Hi,
I am gonna try first creating unique index (hid, pid). It will take a bit
of time and will keep you posted with the result.
Thanks a lot
Gaurav
On Thu, Nov 24, 2011 at 2:08 AM, Simon Slavin wrote:
>
> On 24 Nov 2011, at 7:54am, Gaurav Vyas wrote:
>
> > when I do typeof(hid), it gives "rea
On 24 Nov 2011, at 7:54am, Gaurav Vyas wrote:
> when I do typeof(hid), it gives "real".
You might look into why it is not storing integers instead. It is faster to
search integers than it is to search real numbers. The hid column in your
table should probably be defined with a type of INTEGE
On 24 Nov 2011, at 7:56am, Gaurav Vyas wrote:
> I used the following syntax to create index
> "CREATE UNIQUE INDEX persons_1x
> ON persons (pid,hid);"
This index cannot be used for a search on your 'hid' column. Imagine you had
it written out, and wanted to find all the records with the same '
On Nov 24, 2011, at 8:56 AM, Gaurav Vyas wrote:
> I used the following syntax to create index
> "CREATE UNIQUE INDEX persons_1x
> ON persons (pid,hid);"
Check you query plan (i.e. explain query plan [1]).
I doubt such index has any use as SQLite doesn't support "index skip scans"
access plan
I used the following syntax to create index
"CREATE UNIQUE INDEX persons_1x
ON persons (pid,hid);"
Gaurav
On Thu, Nov 24, 2011 at 1:54 AM, Petite Abeille wrote:
>
> On Nov 24, 2011, at 8:48 AM, Simon Slavin wrote:
>
> > Is the table indexed on that column ?
>
> And if it is... what's its selecti
On Nov 24, 2011, at 8:48 AM, Simon Slavin wrote:
> Is the table indexed on that column ?
And if it is... what's its selectivity?
What 's the query plan?
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/li
I am using multi threads but using single thread to test the speed. And
when I do typeof(hid), it gives "real".
Table is indexed on that column. I dont have a primary key, will that make
any difference?
Gaurav
On Thu, Nov 24, 2011 at 1:48 AM, Simon Slavin wrote:
>
> On 24 Nov 2011, at 7:45am,
On 24 Nov 2011, at 7:45am, Gaurav Vyas wrote:
> I am trying to get a chunk of rows from a table which has 16 million rows.
> The table is indexed. I am passing the query as "SELECT * FROM persons
> WHERE hid = 5;" and it takes a few minutes to get me the results. Can
> anyone suggest how to make
I am trying to get a chunk of rows from a table which has 16 million rows.
The table is indexed. I am passing the query as "SELECT * FROM persons
WHERE hid = 5;" and it takes a few minutes to get me the results. Can
anyone suggest how to make it faster?
Gaurav
_
/speed.html
P.S. I'm sure someone else will give a better explanation.
> -Original Message-
> From: Cesar David Rodas Maldonado [mailto:[EMAIL PROTECTED]
> Sent: 29 June 2006 16:12
> To: sqlite-users@sqlite.org
> Subject: Re: [sqlite] sqlite too slow for me?
>
>
I have a question for every body...
SQLite was very slow for my inserts (like 5 inserts), with out
sincronization
but when i put BEGIN; before start with my inserts is was faster... like
1000 times more... :D why is that?
On 6/28/06, Cesar David Rodas Maldonado <[EMAIL PROTECTED]> wrote:
I dont know a lot about MySQL... but mysql is not so faster as you think...
I have in my computer the mysql 5 is good, but sqlite is so faster too!!!
but MySQL has a query cache so i think the cache make it seems more
faster than sqlite...
On 6/27/06, Péter Szabó <[EMAIL PROTECTED]> wrot
First, thank you all for the answers.
UNIQUE(col1, col4, col5, col2),
Adding this would surely make the query run faster -- provided that
SQLite chooses the right index. But I also use the UNIQUE(col1, col4,
col5) constraint to ensure the uniqueness of these three columns. So
instead I shou
--- [EMAIL PROTECTED] wrote:
> "=?ISO-8859-1?Q?P=E9ter_Szab=F3?=" <[EMAIL PROTECTED]> wrote:
> >
> > My schema is the following:
> >
> > CREATE TABLE t (
> > col1 text NOT NULL,
> > col2 integer NOT NULL,
> > col3 integer NOT NULL,
> > col4 text NOT NULL,
> > col5 text NOT N
"=?ISO-8859-1?Q?P=E9ter_Szab=F3?=" <[EMAIL PROTECTED]> wrote:
>
> My schema is the following:
>
> CREATE TABLE t (
> col1 text NOT NULL,
> col2 integer NOT NULL,
> col3 integer NOT NULL,
> col4 text NOT NULL,
> col5 text NOT NULL,
> PRIMARY KEY(col1, col2, col3, col4, co
Since col1 is always equal to 'foobar' in your data set,
you want to discourage its use by the SQLite optimizer by
using +col1 in the where clause. Any operation on
a column in the where clause disqualifies it from be used
in an index in SQLite.
SELECT col2 FROM t
WHERE +col1='foobar' AND co
"P?ter Szab?" <[EMAIL PROTECTED]> wrote:
> Dear SQLite Developers,
>
> I am seeking help for optimizing my SQLite SQL query, which seems to
> be running unreasonably slow. The query is:
>
> SELECT col2 FROM t WHERE col1='foobar' AND
> col4='foobarfoobarfoobarfoob';
>
> My schema is the follo
Dear SQLite Developers,
I am seeking help for optimizing my SQLite SQL query, which seems to
be running unreasonably slow. The query is:
SELECT col2 FROM t WHERE col1='foobar' AND
col4='foobarfoobarfoobarfoob';
My schema is the following:
CREATE TABLE t (
col1 text NOT NULL,
col2 in
23 matches
Mail list logo
