Simply put, Azure table storage is too slow. The best I could get out of it was about 700 records\/second for INSERT and 4600 records second for READ, which was unacceptable for the data sizes I had to deal with – several tables of around 100,000 records each.<\/p>\n
Admittedly, I did not use batch operations, but it does not seem to matter: 700 records\/second appears to be the true speed of the storage and it can’t be improved: see this StackOverflow article<\/a>.<\/p>\n SQL Server, on the other hand, gave me and 1800-5000 records\/second on INSERT (depending on the record size), and 30,000 records on READ, so I ditched the Table storage and went with the SQL server instead.<\/p>\n The data is summarized in the table below. Each value is records per second, higher values are better.<\/p>\n
| <\/th>\n | Table Storage<\/th>\n | SQL Server<\/th>\n<\/tr>\n |
|---|---|---|
| Read from Azure VM<\/td>\n | 4601<\/td>\n | 30332<\/td>\n<\/tr>\n |
| Write from Azure VM<\/td>\n | 690<\/td>\n | 1867<\/td>\n<\/tr>\n |
| Read from outside Azure<\/td>\n | 3858<\/td>\n | 34456<\/td>\n<\/tr>\n |
| Write from Azure VM<\/td>\n | 213<\/td>\n | 1020<\/td>\n<\/tr>\n<\/table>\n Of course, the speed is highly variable depending on server load, network conditions and the like, but the upper limit of 700 records\/second for table storage INSERT appears to be quite stable.<\/p>\n","protected":false},"excerpt":{"rendered":" |