Markus, Table has exactly 5701 events and need 0.15 seconds per one event for insertion An empty table needs 0.1 seconds here. The time spent in python is too little to be mentioned. Sadly its the commit that takes most of the time. Inserting 10 events in my 5701 events database takes 1.0 seconds 0.15 is very slow for inserting one item IMHO, I would expect 0.01 seconds at minimum, Especially if we intend to deploy on ARM powered devices these times are not acceptable. You could feel a tiny lag at 0.6 second on the Maemo.
** Description changed: We insert pretty slowly with an average of 0.15 seconds for one event on my core i5 2.5 GHz beast. RainCT had some optimization possibilities: 1) PRAGMA synchronous=OFF 2) PRAGMA journal_mode=OFF The Chat: ------------------------------------------------------------ <kamstrup> I think we are - but I can't recall... in case of failed transactions - but I don't even know if we use transactions these days... <seif> <RainCT> try synchronous=OFF <seif> <RainCT> but it can corrupt your database if your phone dies while ZG is inserting <seif> <RainCT> and journal_mode=MEMORY <seif> <RainCT> or OFF since we don't use rollback anyway <seif> so maybe journal_mode = OFF is a good start? <kamstrup> okay, he's probably right... <kamstrup> 'grep -Ri rollback _zeitgeist/' is your friend :-) <kamstrup> apparently we are not using rollback... More info can be found here: http://www.sqlite.org/pragma.html + ------------------------------------------------------------ + + In order to get a better picture of what's going on, can you please try to get some more information, like: + 1) How many events are in your database? + 2) What's the insertion time for one event into an empty db? + 3) Out of this 0.15 secs, how many time is spend in our python code, and what's the time of the actual sql action? + 4) How much faster is adding 10 events at once compared to adding them one at a time? + 5) You think 0.15 secs is slow for inserting one event, what time do you expect, and why? -- Improve insertion times https://bugs.launchpad.net/bugs/639737 You received this bug notification because you are a member of Zeitgeist Framework Team, which is subscribed to Zeitgeist Framework. Status in Zeitgeist Framework: Triaged Bug description: We insert pretty slowly with an average of 0.15 seconds for one event on my core i5 2.5 GHz beast. RainCT had some optimization possibilities: 1) PRAGMA synchronous=OFF 2) PRAGMA journal_mode=OFF The Chat: ------------------------------------------------------------ <kamstrup> I think we are - but I can't recall... in case of failed transactions - but I don't even know if we use transactions these days... <seif> <RainCT> try synchronous=OFF <seif> <RainCT> but it can corrupt your database if your phone dies while ZG is inserting <seif> <RainCT> and journal_mode=MEMORY <seif> <RainCT> or OFF since we don't use rollback anyway <seif> so maybe journal_mode = OFF is a good start? <kamstrup> okay, he's probably right... <kamstrup> 'grep -Ri rollback _zeitgeist/' is your friend :-) <kamstrup> apparently we are not using rollback... More info can be found here: http://www.sqlite.org/pragma.html ------------------------------------------------------------ In order to get a better picture of what's going on, can you please try to get some more information, like: 1) How many events are in your database? 2) What's the insertion time for one event into an empty db? 3) Out of this 0.15 secs, how many time is spend in our python code, and what's the time of the actual sql action? 4) How much faster is adding 10 events at once compared to adding them one at a time? 5) You think 0.15 secs is slow for inserting one event, what time do you expect, and why? _______________________________________________ Mailing list: https://launchpad.net/~zeitgeist Post to : zeitgeist@lists.launchpad.net Unsubscribe : https://launchpad.net/~zeitgeist More help : https://help.launchpad.net/ListHelp
