Mitch I would add -
0. Get onto a connection with faster up speed (3,000 connections = one FSAM, to the NBN for my suburb, work starting May 2011) :-) _____ Ian Thomas Victoria Park, Western Australia _____ From: [email protected] [mailto:[email protected]] On Behalf Of Mitch Denny Sent: Wednesday, November 24, 2010 6:07 AM To: ozDotNet Subject: RE: Azure DB performance Hi Greg, To be honest, this is to be expected. You are accessing a SQL database across the Internet. I'm not sure whether a SQL database on a standard SQL server hosting package would be that much different. You could expect the same kind of issues on a stock standard client/server application running across a corporate WAN. The result? You change your applications to support the network topology. For example, you might adopt the following strategies: 1. Make less requests, but perhaps transfer more data optimistically. 2. You make more requests, but you pre-fetch data based on likely usage patterns. a. I've worked on various applications where the second tab in a dialog was fetched in the background after the first tabs worth of information was fetched and displayed to the user. 3. Adopt a data synchronisation model to cope with network latency and variable connection quality. Regards Mitch Denny Readify | Chief Technology Officer Suite 408 Life.Lab Building | 198 Harbour Esplanade | Docklands | VIC 3008 | Australia M: +61 414 610 141 | E: <mailto:[email protected]> [email protected] | W: <http://www.readify.net/> www.readify.net Description: Description: cid:[email protected] The content of this e-mail, including any attachments is a confidential communication between Readify Pty Ltd and the intended addressee and is for the sole use of that intended addressee. If you are not the intended addressee, any use, interference with, disclosure or copying of this material is unauthorized and prohibited. If you have received this e-mail in error please contact the sender immediately and then delete the message and any attachment(s). From: [email protected] [mailto:[email protected]] On Behalf Of Greg Keogh Sent: Wednesday, 24 November 2010 8:19 AM To: 'ozDotNet' Subject: RE: Azure DB performance I claim my estimates of 5 minutes for insert of 1177 rows vs 2 seconds the select * is in the correct range. I have ADSL2 via Exetel. The insert calls were inside a DataReader loop and I had prepared the DataCommand parameters outside of the loop, setting the values inside the loop. I'm sure the code was sensible. I expect to be running a lot more Azure DB tests over the coming weeks, so perhaps a pattern will become clearer. I am certainly concerned by the poor insert performance, as it's so bad that it could cripple an application at times. We'll see... Greg _____ No virus found in this message. Checked by AVG - www.avg.com Version: 10.0.1153 / Virus Database: 424/3273 - Release Date: 11/22/10
<<image001.gif>>
