Have you run your bare metal test using the same share? And have you tried "pragma synchronous=OFF" ??
And I assume you are using transactions? Have you profiled your app to see where it's spinning? Probably trying to get the lock on the share. What flags did you use to comiple the sqlite library? In particular for threadsafe? Michael D. Black Senior Scientist Advanced Analytics Directorate Advanced GEOINT Solutions Operating Unit Northrop Grumman Information Systems From: sqlite-users-boun...@sqlite.org [sqlite-users-boun...@sqlite.org] on behalf of IQuant [sql...@iquant.co.cc] Sent: Monday, June 04, 2012 11:48 PM To: sqlite-users@sqlite.org Subject: EXT :[sqlite] 100% CPU utilization sqlite running in VMWare Have a market data extractor running tick tapes and saving data to sqlite db. All coded in C++ and previously ran fine and fast on bare metal. Processes tick tapes from NAS and saved to local sqlite db's on c drive. We moved program onto VMWare VM's... same nas tick tapes. Writing db's to a share. On a 4 core vm we can run 3 extractors concurrently at 25 - 75% CPU utilization. The 4th pegs the CPU at 100% Same on an 8 core VM ... seems we can run Cores - 1 without pegging the CPU. The memory footprint for the program is a tiny 9mb... On bare metal we can run 20 extractors concurrently. Looking for suggestions on how to optimize for VMware. _______________________________________________ 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
