I wrote an online/offline app that uses localserver and a gears DB to store data. The app downloads data for 25 tables, and then uses a gears worker to insert that data into the local db. I'm using transactions to encapsulate the table inserts. This works fine on Firefox 3.5 and IE 8. It is really slow running on Chrome (3.0.195.21). On Chrome, it ends up crashing when inserting the data. I get this message: "The following plugin is unresponsive: unknown. Would you like to stop it?" I also get this message: "The following pages have become unresponsive. ..."
If I tell it to continue, it will eventually finish the inserts, but is taking way too long. IE and FF both take about 20 seconds to complete, with no script timeout errors. Chrome is taking about 100 seconds to complete, with error popups. Then, when running offline in Chrome, the app is slow because of the db access, big pauses where it goes to the db for data. It's not bad in FF/IE. It just seems like anything involving the DB access in Chrome is much slower than IE and FF. I want to recommend Chrome as the default browser for this application since the javascript/dom stuff is fast, but the gears DB performance is a problem. Has anyone else seen this or have any suggestions that might improve the Chrome db performance. Does it maybe have to do with gears being in-process in IE/FF but out of process in Chrome? -mark
