Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>In addition to the suggestions of <a href="http://blogs.msdn.com/b/windowsazurestorage/archive/2010/06/25/nagle-s-algorithm-is-not-friendly-towards-small-requests.aspx" rel="noreferrer">Disabling Nagling</a>, there is an extremely nice post on <a href="http://social.technet.microsoft.com/Forums/en-US/windowsazuredata/thread/d84ba34b-b0e0-4961-a167-bbe7618beb83" rel="noreferrer">improving performance of Azure Table Storage</a>. Actually <strong>improving the speed of ADO.NET Deserialization provided 10x speed-up</strong> for <a href="http://www.sqwarea.com/" rel="noreferrer">Sqwarea</a> (massive online multiplayer game built with <a href="http://code.google.com/p/lokad-cloud/" rel="noreferrer">Lokad.Cloud</a> framework).</p> <p>However, <strong>table storage might not be the best solution for huge storage scenarios</strong> (more than millions of records). <strong>Latency is the killing factor here</strong>. To work around that, I've been successfully using file-based database storages, where changes are done locally (without any network latency of CLAP) and are committed to BLOB by uploading the file back (concurrency and scaling out was enforced here by <a href="http://code.google.com/p/lokad-cqrs/" rel="noreferrer">Lokad.CQRS</a> App Engine for Windows Azure).</p> <p>Inserting 10 millions of records to SQLite database at once (within transaction, where each record was indexed by 2 fields and had arbitrary schema-less data serialized via ProtoBuf) took only 200 seconds in total on the average. Uploading/downloading resulting file - roughly 15 seconds on the average. Random reads by index - instantaneous (provided the file is cached in the local storage and ETag is matching).</p>
    singulars
    1. This table or related slice is empty.
    1. POHow to download 100 million rows from Azure Table Storage FAST
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USGregory
    1. USRinat Abdullin
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POHow to download 100 million rows from Azure Table Storage FAST
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COThanks for your advice. This should end up helping a lot. And I just wanted to say that yes, table storage is not ideal for this many records. It was a work around to being throttled by SQL Azure. The SQL Azure problem has been fixed and we are no longer storing the data in table storage, but we still want the data stored there.
      singulars
      1. PO
      1. USjWoose
    2. COI'm glad I've helped. Table storage is good (although API could've been much better) and irreplaceable for things like storing view data of highly scalable web applications. Yet in scenarios that require extremely low latency and high throughput - it's not the best (just like SQL Azure)
      singulars
      1. PO
      1. USRinat Abdullin
    3. CORinat and jWoose. Azure Table Storage is NOT relational. It is a NoSQL, noschema, distributed database, probably implemented in a way similar to what you describe. Azure Table Storage is specifically designed for Gazillions of records.
      singulars
      1. PO
      1. USPanagiotis Kanavos
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload