Maybe there's something fundamental I'm overlooking here, but 5 mins == 300 seconds. Reads take 2 seconds, so writes are 150x worse than reads, not 30x worse.
Joseph On Tue, Nov 23, 2010 at 11:56 PM, Ian Thomas <[email protected]> wrote: > Assuming you have plain ADSL+ and not something less asymmetric such as > Annexe M or Bonded DSL, or better – you would expect perhaps 20 times worse > performance on upload just because of the internet connection. 5mins to 2 > secs = 30 times. > > > ------------------------------ > > Ian Thomas > Victoria Park, Western Australia > ------------------------------ > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *Greg Keogh > *Sent:* Tuesday, November 23, 2010 7:28 PM > *To:* 'ozDotNet' > *Subject:* Azure DB performance > > > > Folks, after an hour of suffering weird errors I managed to create my first > Azure database and a small console app to copy rows from a local table into > the Azure one. I got a bit of a fright when it took about 5 minutes to > insert the 1177 rows into the Azure table. Luckily however, it only takes > about 2 seconds to read them all back with a DatAdapter.Fill and show the > resulting DataTable in a WinForms grid. > > > > I’m quite surprised by the wildly different timings for inserts vs reads. > Has anyone experienced this? > > > > Is anyone using Azure DBs in anger and has anything startling to report? > Gotchas? > > > > It’s great to be able to have “roaming” databases with such ease just by > tweaking the connection strings. It creates lots of convenient alternatives > for the way disconnected apps can be designed. > > > > Greg > ------------------------------ > > No virus found in this message. > Checked by AVG - www.avg.com > Version: 10.0.1153 / Virus Database: 424/3267 - Release Date: 11/19/10 > -- w: http://jcooney.net t: @josephcooney
