{"version":"1.0","provider_name":"Azure Cosmos DB Blog","provider_url":"https:\/\/devblogs.microsoft.com\/cosmosdb","author_name":"Andy Feldman","author_url":"https:\/\/devblogs.microsoft.com\/cosmosdb\/author\/anfeldma\/","title":"Planning Azure Cosmos DB capacity using vCores, vCPUs, and request rates - Azure Cosmos DB Blog","type":"rich","width":600,"height":338,"html":"<blockquote class=\"wp-embedded-content\" data-secret=\"Pug32x3xps\"><a href=\"https:\/\/devblogs.microsoft.com\/cosmosdb\/cap-planning-vcore\/\">Planning Azure Cosmos DB capacity using vCores, vCPUs, and request rates<\/a><\/blockquote><iframe sandbox=\"allow-scripts\" security=\"restricted\" src=\"https:\/\/devblogs.microsoft.com\/cosmosdb\/cap-planning-vcore\/embed\/#?secret=Pug32x3xps\" width=\"600\" height=\"338\" title=\"&#8220;Planning Azure Cosmos DB capacity using vCores, vCPUs, and request rates&#8221; &#8212; Azure Cosmos DB Blog\" data-secret=\"Pug32x3xps\" frameborder=\"0\" marginwidth=\"0\" marginheight=\"0\" scrolling=\"no\" class=\"wp-embedded-content\"><\/iframe><script>\n\/*! This file is auto-generated *\/\n!function(d,l){\"use strict\";l.querySelector&&d.addEventListener&&\"undefined\"!=typeof URL&&(d.wp=d.wp||{},d.wp.receiveEmbedMessage||(d.wp.receiveEmbedMessage=function(e){var t=e.data;if((t||t.secret||t.message||t.value)&&!\/[^a-zA-Z0-9]\/.test(t.secret)){for(var s,r,n,a=l.querySelectorAll('iframe[data-secret=\"'+t.secret+'\"]'),o=l.querySelectorAll('blockquote[data-secret=\"'+t.secret+'\"]'),c=new RegExp(\"^https?:$\",\"i\"),i=0;i<o.length;i++)o[i].style.display=\"none\";for(i=0;i<a.length;i++)s=a[i],e.source===s.contentWindow&&(s.removeAttribute(\"style\"),\"height\"===t.message?(1e3<(r=parseInt(t.value,10))?r=1e3:~~r<200&&(r=200),s.height=r):\"link\"===t.message&&(r=new URL(s.getAttribute(\"src\")),n=new URL(t.value),c.test(n.protocol))&&n.host===r.host&&l.activeElement===s&&(d.top.location.href=t.value))}},d.addEventListener(\"message\",d.wp.receiveEmbedMessage,!1),l.addEventListener(\"DOMContentLoaded\",function(){for(var e,t,s=l.querySelectorAll(\"iframe.wp-embedded-content\"),r=0;r<s.length;r++)(t=(e=s[r]).getAttribute(\"data-secret\"))||(t=Math.random().toString(36).substring(2,12),e.src+=\"#?secret=\"+t,e.setAttribute(\"data-secret\",t)),e.contentWindow.postMessage({message:\"ready\",secret:t},\"*\")},!1)))}(window,document);\n\/\/# sourceURL=https:\/\/devblogs.microsoft.com\/cosmosdb\/wp-includes\/js\/wp-embed.min.js\n<\/script>\n","thumbnail_url":"https:\/\/devblogs.microsoft.com\/cosmosdb\/wp-content\/uploads\/sites\/52\/2021\/09\/migration_image.png","thumbnail_width":1751,"thumbnail_height":621,"description":"How to use the information you know about your database clusters to estimate the provisioned throughput request units you'll need when migrating NoSQL data to Azure Cosmos DB and avoid over-provisioning or overpaying"}