Neither of these are your problem, but I noticed the following in your posted code:
PRAGMA auto_vacuum=NONE; has no affect after your tables are created. You should move this setting earlier in your code. http://www.sqlite.org/pragma.html#pragma_auto_vacuum PRAGMA count_changes=OFF is deprecated and shouldn't be used. http://www.sqlite.org/pragma.html#pragma_count_changes On Thu, Apr 3, 2014 at 5:41 AM, Simon Slavin <slav...@bigfraud.org> wrote: > > On 3 Apr 2014, at 3:29am, Kevin Xu <accol...@gmail.com> wrote: > > > I have not discovered how to find internal memory throughput usage in > OSX, and I agree that something is not allowing the system from maxing out > the CPU or I/O. > > A single application can max a single core of a single CPU if it tries > hard. So if your bottleneck is CPU then Activity Monitor will show a > section running at 98% or above. If that's not happening, then something > else is your bottleneck -- probably either main memory or main storage. > 'nice' will probably not help unless you are knowingly running other > applications which hog CPU time. On modern Macs the OS tends to use one > core and leave the other cores free for apps. > > If you can't find memory throughput out using the OS X 10.9 version of > Activity Monitor, it's probably only possible to find it out using > profiling tools and a debugger. I don't see a way to find out memory > throughput using Activity Monitor. > > Simon. > _______________________________________________ > sqlite-users mailing list > sqlite-users@sqlite.org > http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users > _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
