Re: [sqlite] "INSERT" and "END TRANSACTION" time

2014-03-04 Thread Stephan Beal
On Tue, Mar 4, 2014 at 3:44 AM, Simon Slavin wrote: > > On 4 Mar 2014, at 1:15am, romtek wrote: > > > I have a question based on my observation. According to your numbers for > a > > 5400 RPM disk, one write op should take about 11 ms. However, it often >

Re: [sqlite] "INSERT" and "END TRANSACTION" time

2014-03-04 Thread Simon Slavin
On 4 Mar 2014, at 5:06am, romtek wrote: > If that were true, then I wouldn't be getting a very large speed-up when > enveloping write ops in an explicit transaction, would I? Sorry, I can't tell. It depends on how the virtual storage mechanism works. But if your

Re: [sqlite] "INSERT" and "END TRANSACTION" time

2014-03-03 Thread romtek
If that were true, then I wouldn't be getting a very large speed-up when enveloping write ops in an explicit transaction, would I? On Mon, Mar 3, 2014 at 8:44 PM, Simon Slavin wrote: > > On 4 Mar 2014, at 1:15am, romtek wrote: > > > I have a question

Re: [sqlite] "INSERT" and "END TRANSACTION" time

2014-03-03 Thread Simon Slavin
On 4 Mar 2014, at 1:15am, romtek wrote: > I have a question based on my observation. According to your numbers for a > 5400 RPM disk, one write op should take about 11 ms. However, it often > takes only about 1 ms on HostGator drives on its shared hosting servers. > Are there

Re: [sqlite] "INSERT" and "END TRANSACTION" time

2014-03-03 Thread romtek
Thank for the clarification, Simon! I have a question based on my observation. According to your numbers for a 5400 RPM disk, one write op should take about 11 ms. However, it often takes only about 1 ms on HostGator drives on its shared hosting servers. Are there drives that are SO much faster

Re: [sqlite] "INSERT" and "END TRANSACTION" time

2014-03-03 Thread Simon Slavin
On 3 Mar 2014, at 9:11pm, romtek wrote: > Simon, does a real disk have to be a rotating hard disk? Is there problem > with SSDs as far as SQLite is concerned? SSDs aren't a problem, and SQLite works fine with them, but they change the timings associated with SQLite a great

Re: [sqlite] "INSERT" and "END TRANSACTION" time

2014-03-03 Thread romtek
> > a normal DB where writing does not happen often I would suggest a SSD... > but anything with a very active read/write cycle is best avoided If you were to quantify this, would you say that "active" starts at once per second, many times per second, once a min or...? On Mon, Mar 3, 2014 at

Re: [sqlite] "INSERT" and "END TRANSACTION" time

2014-03-03 Thread RSmith
On 2014/03/03 23:11, romtek wrote: Simon, does a real disk have to be a rotating hard disk? Is there problem with SSDs as far as SQLite is concerned? No, what Simon is trying to point out is simply that the write performance experienced by L. Wood might be because journal writes might be

Re: [sqlite] "INSERT" and "END TRANSACTION" time

2014-03-03 Thread romtek
Simon, does a real disk have to be a rotating hard disk? Is there problem with SSDs as far as SQLite is concerned? On Mon, Mar 3, 2014 at 2:21 PM, Simon Slavin wrote: > > On 3 Mar 2014, at 6:03pm, L. Wood wrote: > > > _bind() on a prepared statement

Re: [sqlite] "INSERT" and "END TRANSACTION" time

2014-03-03 Thread Simon Slavin
On 3 Mar 2014, at 6:03pm, L. Wood wrote: > _bind() on a prepared statement and execution of "INSERT" are taking 70% of > the time, but the "END TRANSACTION" only 30% of the time. > > The time between _bind() and execution of "INSERT" is roughly 50/50, so it's > a total of: