/MD /W3 /GX /O2 /Ob2 /D "NDEBUG" /D "WIN32" /D "_LIB" /D "_AFXDLL" /Fp"Release/LibSqlite3.pch" /YX /Fo"Release/" /Fd"Release/" /FD /c
Thx!
Since SQLite seems to be I/O bound, I'm not sure the compiler matters that much. What I find is that performance on SCSI equipped machines is far superior to IDE. In some case I've had perfectly acceptable performance on my SCSI based system which becomes unusable when on my customers IDE based systems. Not SQlite's fault, IDE and SATA drives just aren't so hot.
Well, I got another mail saying that my app will probably be disk bound, but that's not really the case for my application: - I insert data in huge transactions (a kind of bulk load) - The application reads the data most of the time. And it reads the data sequentially. Therefore it is mostly CPU bound. - I use a trick to speed up access: I read the data once in 'natural order'. This puts the data into the system disk cache. From then on, access is *much* faster compared to a setup where I don't read the data once initially. Michael
