> ahhh... now we are getting somewhere. > > Here is a suggestion... start a new thread, with a clear and relevant > subject line, describe your app succinctly, note that it works on such > and such machine, and that it fails to work on such and such machine, > describe exactly what "does not run" mean -- does it not start, does > it start and then hang, does it start and then quit, does it give an > error message, etc., describe the specs of the machine it does not > work on... > > That would be very helpful to all. > Hi,
I understand what you are saying, but again, there is no such thing (yet). I am finishing off my application and would like to prepare it to the best. I already got feedback that it is stalling sometimes when running from DVD, yet the database is also fighting with another vital part of the application, which is the tile loader (for the graphical patches on the globe). I can also give you my machine specs, yet my client is unable to produce a lowest common denominator spec machine on which the app still must run. Furthermore, I am not your average user - i use sqlite in a multimedia authoring program called Adobe Director, and I got a code extension for the app (a so-called Xtra), as well as an external (threaded) shell running sqlite3.exe for repeated queries on a city database in order to show the name of the cities currently visible. Other than that, i am on Windows XP, yet the app is ought to run on Win2K, WinXP and Vista with a 1.6 GHz CPU, 1 GB of RAM and a 3d graphics card and DVD drive. My dev machine is different of course (2Ghz, 2GB of RAM, Windows XP). Does it run? Yes. Does it run fast? For me here, yes, it does. Does it run fast enough? Does an application ever run fast enough? I am tweaking it to the max, also considering Dr Hipps compression extension in order to squeeze out the maximum amount of speed available in order to let the application run on a maximum of machines. We are currently facing stalling of the app when loading tiles and querying the database, especially at a mid-size altitude from earth, where class>2 cities are being shown (class of the city = its importance). It is a typical loading bottleneck between pulling graphics in (threaded as well) and querying/loading database content. Since the DVD can only load one thing at a time, the queries for the database get apparently stalled in the thread until the DVD hits the database file again and executes them. I have experiemented extensively with caching, making the cache size high, low and medium - to no avail, the sheer amount of data (the size of the database) is to big. We have 90Mb of data. Situation got better when we yanked class 6 "cities" (small towns) which made up 2/3 of the database. I am currently doing in-memory databases of the most important stuff in order to speed up the queries and get it to work. So all in all, i am already finetuning, yet to a target "system" which is at my client´s site through educated guesses in the code. -- Christophe Leske www.multimedial.de - [EMAIL PROTECTED] http://www.linkedin.com/in/multimedial Lessingstr. 5 - 40227 Duesseldorf - Germany 0211 261 32 12 - 0177 249 70 31 _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
