{"id":200,"date":"2025-12-28T02:00:03","date_gmt":"2025-12-28T02:00:03","guid":{"rendered":"https:\/\/windows-vps.org\/blog\/?p=200"},"modified":"2026-11-03T22:06:43","modified_gmt":"2026-11-03T22:06:43","slug":"mpio-multipath-io-disk-latency-vps","status":"publish","type":"post","link":"https:\/\/windows-vps.org\/blog\/mpio-multipath-io-disk-latency-vps\/","title":{"rendered":"MPIO on a Windows VPS: When Multiple Disk Paths Actually Reduce Latency"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\">Two paths to the same LUN look like free redundancy on paper. In practice, most Windows VPS instances that bolt on MPIO gain 3\u20135 ms of steady-state latency instead of losing it, because the paths end at the same virtual storage array and the additional I\/O dispatch only adds queuing. Multipath I\/O is not a magic latency reducer; it is an availability mechanism with a measurable cost, and the numbers decide whether you keep it.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The mechanics are straightforward. Windows MPIO loads a vendor or Microsoft DSM, claims disks with multiple device instances, and presents a single disk object with a load-balancing policy \u2014 round robin, least queue depth, or failover only. Every additional path multiplies the I\/O stack depth, the number of outstanding requests, and the chance that two paths to the same backing store contend for the same queue.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The first question is not &#8220;how many paths&#8221; but &#8220;do these paths terminate on physically separate controllers?&#8221; On a <a href=\"https:\/\/windows-vps.org\/\">Windows VPS rented from a shared platform<\/a>, iSCSI targets often share a storage NIC or even a storage node, so two sessions = one queue behind the scenes. Check with <code>mpclaim -s -d<\/code> whether both paths carry distinct target portal addresses and distinct initiator adapters.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">When a second path helps<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">A second path genuinely helps when it crosses a failure domain: two separate network adapters, two switches, two target portals on different storage controllers. In that topology, failover recovers from a dead HBA in under 30 seconds with the Microsoft DSM&#8217;s default retry timers, and least-queue-depth balancing distributes bursts across two real queues. That is a real latency win during a failure, not in steady state.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">It also helps when the first path saturates. A single 1 Gbps iSCSI session tops out around 118 MB\/s; two sessions on separate adapters can push roughly 235 MB\/s if the backing store can serve it. If your VPS disk queue length sits pinned at 2 or higher on a single path and CPU is idle, extra bandwidth is the bottleneck, and a second path can cut average latency by 20\u201340%.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">When a second path hurts<\/h2>\n\n\n\n<ul class=\"wp-block-list\"><li>Both sessions to the same target IP \u2014 you get a second session, not a second queue.<\/li>\n<li>Round-robin on a storage array that does not deduplicate write cache, so writes land twice.<\/li>\n<li>Guest-level MPIO layered over host-level storage replication, doubling the retry budget.<\/li>\n<li>Small random reads where per-request dispatch overhead dominates the actual transfer.<\/li><\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">The latency signature of the bad case is specific: average latency rises 2\u20136 ms, but maximum latency and the 99th percentile rise far more, because requests queue behind a single backend. IOPS as reported by the guest look higher while throughput stays flat \u2014 the classic sign of splitting one queue into two visible ones. If you see that, drop back to failover-only policy.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Verifying with Performance Monitor<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Three counter sets carry the whole story. Disk counters give per-physical-disk latency and queue depth; MPIO counters give per-path bytes and I\/O counts; Network Interface counters show whether the sessions actually use separate NICs. Add them to a data collector set at 1-second sampling for a 10-minute capture under a realistic workload, not a synthetic single-thread copy.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>Get-Counter -Counter @(\n \"\\PhysicalDisk(*)\\Avg. Disk sec\/Read\",\n \"\\PhysicalDisk(*)\\Current Disk Queue Length\",\n \"\\MPIO Disk(*)\\Read Bytes\/sec\",\n \"\\Network Interface(*)\\Bytes Total\/sec\") -SampleInterval 1 -MaxSamples 600<\/code><\/pre>\n\n\n\n<figure class=\"wp-block-table\"><table><thead><tr><th>Counter<\/th><th>Healthy<\/th><th>Investigate<\/th><th>Problem<\/th><\/tr><\/thead><tbody><tr><td>Avg. Disk sec\/Read<\/td><td>&lt; 0.010<\/td><td>0.010\u20130.025<\/td><td>&gt; 0.025<\/td><\/tr><tr><td>Avg. Disk sec\/Write<\/td><td>&lt; 0.015<\/td><td>0.015\u20130.040<\/td><td>&gt; 0.040<\/td><\/tr><tr><td>Current Disk Queue Length<\/td><td>0\u20131<\/td><td>2\u20134<\/td><td>&gt; 4 sustained<\/td><\/tr><tr><td>Path 0 vs Path 1 bytes\/sec<\/td><td>within 20%<\/td><td>20\u201350% skew<\/td><td>one path idle<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<h2 class=\"wp-block-heading\">Counting the paths correctly<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Windows does not expose MPIO paths as separate physical disks in the Disk performance set unless the DSM registers them. Use <code>mpclaim -s -d<\/code> for the path inventory and <code>mpclaim -s -d &lt;number&gt;<\/code> for per-path state, then cross-check that the MPIO Disk counter set lists the same number of instances. Mismatch means the DSM is not aggregating and you are measuring one path while believing you have two.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Also confirm the load-balancing policy actually applied. <code>mpclaim -l<\/code> shows the current policy per disk. A common misconfiguration is setting round robin via the GUI while a group policy or vendor DSM resets it to failover-only on reboot \u2014 you will see one path carrying zero bytes in the counter table and assume the storage is broken. Set the policy explicitly and re-verify after a restart.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Guarding the timeout and retry budget<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Every additional path multiplies the time the I\/O manager spends waiting before it declares the LUN dead. Default disk timeouts of 60 seconds per path mean a two-path failover can stall an application for two minutes if both paths are retried sequentially. Lower <code>TimeOutValue<\/code> under the disk&#8217;s registry parameters to 20\u201330 seconds and test the failover by pulling one NIC while a workload runs.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Measure the pause directly. A simple loop writing a timestamped file every second will show you a gap where the failover happened. Anything over 10 seconds needs the DSM retry count reduced, and if the application cannot tolerate a 30-second pause at all, MPIO is the wrong answer \u2014 use application-level retry and a single robust path instead.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Decision table for VPS workloads<\/h2>\n\n\n\n<figure class=\"wp-block-table\"><table><thead><tr><th>Workload<\/th><th>Paths<\/th><th>Policy<\/th><th>Reason<\/th><\/tr><\/thead><tbody><tr><td>SQL Server data files<\/td><td>2 on separate HBAs<\/td><td>Least queue depth<\/td><td>Burst absorption<\/td><\/tr><tr><td>Web\/app tier, stateless<\/td><td>1<\/td><td>n\/a<\/td><td>Restart is cheaper<\/td><\/tr><tr><td>Large sequential backup<\/td><td>2<\/td><td>Round robin<\/td><td>Throughput ceiling<\/td><\/tr><tr><td>Same-target dual session<\/td><td>1<\/td><td>Failover only<\/td><td>No second queue<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<h2 class=\"wp-block-heading\">After the change<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Change one variable at a time. Record the baseline counter set, add the second path, re-capture, and compare p50 and p95 rather than averages \u2014 averages hide the queuing spikes that make MPIO look good on a dashboard and bad in production. Keep the capture files for two weeks so a later slowdown can be compared against the pre-change state.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">If the numbers do not improve, remove the extra path. That is a legitimate outcome and it frees an adapter for backup traffic or a management network. Multipath I\/O earns its place at the storage layer, not the marketing layer; on a <a href=\"https:\/\/windows-vps.org\/\">Windows VPS host you control end to end<\/a>, you can test both configurations in an afternoon and keep whichever wins on p95 latency.<\/p>\n\n","protected":false},"excerpt":{"rendered":"<p>If you&#8217;re looking to enhance your online presence or need a reliable server for your applications, using a Windows VPS (Virtual Private Server) can be a game changer. In this guide, we&#8217;ll explore how to effectively use a Windows VPS, covering everything from setup to optimization. For more detailed resources.<\/p>\n","protected":false},"author":1,"featured_media":201,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"iawp_total_views":5,"footnotes":""},"categories":[5],"tags":[],"class_list":["post-200","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-tutorials-guides"],"yoast_head":"<!-- This site is optimized with the Yoast SEO Premium plugin v26.1 (Yoast SEO v26.1) - https:\/\/yoast.com\/wordpress\/plugins\/seo\/ -->\n<title>MPIO on a Windows VPS: When Multiple Disk Paths Actually Reduce Latency - Windows VPS Blog<\/title>\n<meta name=\"description\" content=\"If you&#039;re looking to enhance your online presence or need a reliable server for your applications, using a Windows VPS (Virtual Private Server) can be a game changer. In this guide, we&#039;ll explore how to effectively use a Windows VPS, covering everything from setup to optimization. For more detailed resources.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/windows-vps.org\/blog\/mpio-multipath-io-disk-latency-vps\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"MPIO on a Windows VPS: When Multiple Disk Paths Actually Reduce Latency\" \/>\n<meta property=\"og:description\" content=\"MPIO on a Windows VPS: When Multiple Disk Paths Actually Reduce Latency\" \/>\n<meta property=\"og:url\" content=\"https:\/\/windows-vps.org\/blog\/mpio-multipath-io-disk-latency-vps\/\" \/>\n<meta property=\"og:site_name\" content=\"Windows VPS Blog\" \/>\n<meta property=\"article:published_time\" content=\"2025-12-28T02:00:03+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2026-11-03T22:06:43+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/windows-vps.org\/blog\/wp-content\/uploads\/2025\/12\/33669-1.jpg\" \/>\n\t<meta property=\"og:image:width\" content=\"960\" \/>\n\t<meta property=\"og:image:height\" content=\"640\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/jpeg\" \/>\n<meta name=\"author\" content=\"windows-vps\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:creator\" content=\"@myxiechengxuan\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"windows-vps\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"3 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\/\/windows-vps.org\/blog\/mpio-multipath-io-disk-latency-vps\/\",\"url\":\"https:\/\/windows-vps.org\/blog\/mpio-multipath-io-disk-latency-vps\/\",\"name\":\"MPIO on a Windows VPS: When Multiple Disk Paths Actually Reduce Latency - Windows VPS Blog\",\"isPartOf\":{\"@id\":\"https:\/\/windows-vps.org\/blog\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\/\/windows-vps.org\/blog\/mpio-multipath-io-disk-latency-vps\/#primaryimage\"},\"image\":{\"@id\":\"https:\/\/windows-vps.org\/blog\/mpio-multipath-io-disk-latency-vps\/#primaryimage\"},\"thumbnailUrl\":\"https:\/\/windows-vps.org\/blog\/wp-content\/uploads\/2025\/12\/33669-1.jpg\",\"datePublished\":\"2025-12-28T02:00:03+00:00\",\"dateModified\":\"2026-11-03T22:06:43+00:00\",\"author\":{\"@id\":\"https:\/\/windows-vps.org\/blog\/#\/schema\/person\/44caceed916d0db318aa08d5623a7a58\"},\"description\":\"If you're looking to enhance your online presence or need a reliable server for your applications, using a Windows VPS (Virtual Private Server) can be a game changer. In this guide, we'll explore how to effectively use a Windows VPS, covering everything from setup to optimization. For more detailed resources.\",\"breadcrumb\":{\"@id\":\"https:\/\/windows-vps.org\/blog\/mpio-multipath-io-disk-latency-vps\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/windows-vps.org\/blog\/mpio-multipath-io-disk-latency-vps\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/windows-vps.org\/blog\/mpio-multipath-io-disk-latency-vps\/#primaryimage\",\"url\":\"https:\/\/windows-vps.org\/blog\/wp-content\/uploads\/2025\/12\/33669-1.jpg\",\"contentUrl\":\"https:\/\/windows-vps.org\/blog\/wp-content\/uploads\/2025\/12\/33669-1.jpg\",\"width\":960,\"height\":640},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/windows-vps.org\/blog\/mpio-multipath-io-disk-latency-vps\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/windows-vps.org\/blog\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"MPIO on a Windows VPS: When Multiple Disk Paths Actually Reduce Latency\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/windows-vps.org\/blog\/#website\",\"url\":\"https:\/\/windows-vps.org\/blog\/\",\"name\":\"Windows VPS Blog\",\"description\":\"\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/windows-vps.org\/blog\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Person\",\"@id\":\"https:\/\/windows-vps.org\/blog\/#\/schema\/person\/44caceed916d0db318aa08d5623a7a58\",\"name\":\"windows-vps\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/windows-vps.org\/blog\/#\/schema\/person\/image\/\",\"url\":\"https:\/\/secure.gravatar.com\/avatar\/3f2573db5afcd1a6ab9abcc5d48fc8e42584bc87ab9d98cc156e5b2097766dd9?s=96&d=mm&r=g\",\"contentUrl\":\"https:\/\/secure.gravatar.com\/avatar\/3f2573db5afcd1a6ab9abcc5d48fc8e42584bc87ab9d98cc156e5b2097766dd9?s=96&d=mm&r=g\",\"caption\":\"windows-vps\"},\"sameAs\":[\"https:\/\/windows-vps.org\/blog\",\"https:\/\/x.com\/myxiechengxuan\"],\"url\":\"https:\/\/windows-vps.org\/blog\/author\/myxiechengxuan\/\"}]}<\/script>\n<!-- \/ Yoast SEO Premium plugin. -->","yoast_head_json":{"title":"MPIO on a Windows VPS: When Multiple Disk Paths Actually Reduce Latency - Windows VPS Blog","description":"If you're looking to enhance your online presence or need a reliable server for your applications, using a Windows VPS (Virtual Private Server) can be a game changer. In this guide, we'll explore how to effectively use a Windows VPS, covering everything from setup to optimization. For more detailed resources.","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/windows-vps.org\/blog\/mpio-multipath-io-disk-latency-vps\/","og_locale":"en_US","og_type":"article","og_title":"MPIO on a Windows VPS: When Multiple Disk Paths Actually Reduce Latency","og_description":"MPIO on a Windows VPS: When Multiple Disk Paths Actually Reduce Latency","og_url":"https:\/\/windows-vps.org\/blog\/mpio-multipath-io-disk-latency-vps\/","og_site_name":"Windows VPS Blog","article_published_time":"2025-12-28T02:00:03+00:00","article_modified_time":"2026-11-03T22:06:43+00:00","og_image":[{"width":960,"height":640,"url":"https:\/\/windows-vps.org\/blog\/wp-content\/uploads\/2025\/12\/33669-1.jpg","type":"image\/jpeg"}],"author":"windows-vps","twitter_card":"summary_large_image","twitter_creator":"@myxiechengxuan","twitter_misc":{"Written by":"windows-vps","Est. reading time":"3 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/windows-vps.org\/blog\/mpio-multipath-io-disk-latency-vps\/","url":"https:\/\/windows-vps.org\/blog\/mpio-multipath-io-disk-latency-vps\/","name":"MPIO on a Windows VPS: When Multiple Disk Paths Actually Reduce Latency - Windows VPS Blog","isPartOf":{"@id":"https:\/\/windows-vps.org\/blog\/#website"},"primaryImageOfPage":{"@id":"https:\/\/windows-vps.org\/blog\/mpio-multipath-io-disk-latency-vps\/#primaryimage"},"image":{"@id":"https:\/\/windows-vps.org\/blog\/mpio-multipath-io-disk-latency-vps\/#primaryimage"},"thumbnailUrl":"https:\/\/windows-vps.org\/blog\/wp-content\/uploads\/2025\/12\/33669-1.jpg","datePublished":"2025-12-28T02:00:03+00:00","dateModified":"2026-11-03T22:06:43+00:00","author":{"@id":"https:\/\/windows-vps.org\/blog\/#\/schema\/person\/44caceed916d0db318aa08d5623a7a58"},"description":"If you're looking to enhance your online presence or need a reliable server for your applications, using a Windows VPS (Virtual Private Server) can be a game changer. In this guide, we'll explore how to effectively use a Windows VPS, covering everything from setup to optimization. For more detailed resources.","breadcrumb":{"@id":"https:\/\/windows-vps.org\/blog\/mpio-multipath-io-disk-latency-vps\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/windows-vps.org\/blog\/mpio-multipath-io-disk-latency-vps\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/windows-vps.org\/blog\/mpio-multipath-io-disk-latency-vps\/#primaryimage","url":"https:\/\/windows-vps.org\/blog\/wp-content\/uploads\/2025\/12\/33669-1.jpg","contentUrl":"https:\/\/windows-vps.org\/blog\/wp-content\/uploads\/2025\/12\/33669-1.jpg","width":960,"height":640},{"@type":"BreadcrumbList","@id":"https:\/\/windows-vps.org\/blog\/mpio-multipath-io-disk-latency-vps\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/windows-vps.org\/blog\/"},{"@type":"ListItem","position":2,"name":"MPIO on a Windows VPS: When Multiple Disk Paths Actually Reduce Latency"}]},{"@type":"WebSite","@id":"https:\/\/windows-vps.org\/blog\/#website","url":"https:\/\/windows-vps.org\/blog\/","name":"Windows VPS Blog","description":"","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/windows-vps.org\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Person","@id":"https:\/\/windows-vps.org\/blog\/#\/schema\/person\/44caceed916d0db318aa08d5623a7a58","name":"windows-vps","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/windows-vps.org\/blog\/#\/schema\/person\/image\/","url":"https:\/\/secure.gravatar.com\/avatar\/3f2573db5afcd1a6ab9abcc5d48fc8e42584bc87ab9d98cc156e5b2097766dd9?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/3f2573db5afcd1a6ab9abcc5d48fc8e42584bc87ab9d98cc156e5b2097766dd9?s=96&d=mm&r=g","caption":"windows-vps"},"sameAs":["https:\/\/windows-vps.org\/blog","https:\/\/x.com\/myxiechengxuan"],"url":"https:\/\/windows-vps.org\/blog\/author\/myxiechengxuan\/"}]}},"_links":{"self":[{"href":"https:\/\/windows-vps.org\/blog\/wp-json\/wp\/v2\/posts\/200","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/windows-vps.org\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/windows-vps.org\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/windows-vps.org\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/windows-vps.org\/blog\/wp-json\/wp\/v2\/comments?post=200"}],"version-history":[{"count":6,"href":"https:\/\/windows-vps.org\/blog\/wp-json\/wp\/v2\/posts\/200\/revisions"}],"predecessor-version":[{"id":1023,"href":"https:\/\/windows-vps.org\/blog\/wp-json\/wp\/v2\/posts\/200\/revisions\/1023"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/windows-vps.org\/blog\/wp-json\/wp\/v2\/media\/201"}],"wp:attachment":[{"href":"https:\/\/windows-vps.org\/blog\/wp-json\/wp\/v2\/media?parent=200"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/windows-vps.org\/blog\/wp-json\/wp\/v2\/categories?post=200"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/windows-vps.org\/blog\/wp-json\/wp\/v2\/tags?post=200"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}