On Mon, Jul 27, 2015 at 8:42 AM, Richard Hipp <drh at sqlite.org> wrote:
> On 7/27/15, rotaiv <rotaiv at gmail.com> wrote: > > > > My question is ... What is about my machine at home > > that allows Sqlite to query 2 million files so quickly? > > > ?I missed the initial post, somehow.? ?Could there be an index on something on the home machine which does not exist on the work machine? Can you do an EXPLAIN on both to see what the query plan is?? ?Perhaps another major reason would be if the home machine hardware is faster than the other machine?. An extreme example: at work my machine is a very old 2 GiB Pentium system running at 1.8 GiHz with a normal 5400 RPM hard drive. My home machine is a 16 GiB, 3.7 GiHz Xeon with an 320 GiB SSD + 2 TiB 7200 RPM HD. Need I mention how much faster my home machine is? The software configuration is almost identical: Fedora 22 x86_64. I also wonder if the work PC is running other "server" type applications which use up CPU and RAM. Also, is the work PC running 64 bit or 32 bit Linux? How about Windows at home (I assume 64 bit here)? But, in any case, 40 minutes seems really poor performance, unless there is some hardware issue. Also, I agree with Simon that the query itself, and it's use of NULL, looks weird. And I don't see where it could find any matches because the "ON work.fpath = home.fpath" should never match if either fpath is NULL. > > Probably a newer version of SQLite. You didn't tell us the version > numbers for SQLite on the two machines. > -- > D. Richard Hipp > drh at sqlite.org > _______________________________________________ > sqlite-users mailing list > sqlite-users at mailinglists.sqlite.org > http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users > -- Schrodinger's backup: The condition of any backup is unknown until a restore is attempted. Yoda of Borg, we are. Futile, resistance is, yes. Assimilated, you will be. He's about as useful as a wax frying pan. 10 to the 12th power microphones = 1 Megaphone Maranatha! <>< John McKown
