I think either (a) your computer is broken; (b) your database is broken; or, (c) your methodology is broken.
While I cannot speak to the inherent (ample) inefficiencies of dotnot, inserting three times the number of records (that is, ~1 million with multiple indexes) takes one-fifth the time (~1 minute) whether in the command line shell or using Python. Using an on-disk database rather than a :memory: database takes a little longer, but still many times faster than you report (~2 minutes or just under twice as long). You do not report the versions of anything you are using and this information may be somewhat helpful. For example, are you using Sqlite 1.0 on Windows 286 with an 40 Megabyte MFM Hard Disk and 512 KB of RAM, or something a little more modern? --- Theory is when you know everything but nothing works. Practice is when everything works but no one knows why. Sometimes theory and practice are combined: nothing works and no one knows why. >-----Original Message----- >From: [email protected] [mailto:sqlite-users- >[email protected]] On Behalf Of Nihar Dash >Sent: Wednesday, 31 December, 2014 14:23 >To: [email protected] >Subject: [sqlite] Question regarding Sqlite In-Memory DB Insert > >HiI am using SQLite In-Memory DB for loading cache data into memory. I am >using dotnet. The data I am inserting are .3 million. When I use the same >number of records to insert in Console App it takes around 5 min. However >If I host my app in IIS and Insert the same number of records It takes 60 >minutes. No change in logic The DataSource is flat file. I am curious why >the insert is so slow when hosted in IIS? I tried to search but did to >get any answer. Any help here is highly appreciated. thanksNihar >_______________________________________________ >sqlite-users mailing list >[email protected] >http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users _______________________________________________ sqlite-users mailing list [email protected] http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
