<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://icstaging.mywikis.net/w/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Jdobbs</id>
	<title>Internet Computer Wiki Staging - User contributions [en]</title>
	<link rel="self" type="application/atom+xml" href="https://icstaging.mywikis.net/w/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Jdobbs"/>
	<link rel="alternate" type="text/html" href="https://icstaging.mywikis.net/wiki/Special:Contributions/Jdobbs"/>
	<updated>2026-04-20T00:08:11Z</updated>
	<subtitle>User contributions</subtitle>
	<generator>MediaWiki 1.39.17</generator>
	<entry>
		<id>https://icstaging.mywikis.net/w/index.php?title=ELI5:_How_fast_is_the_Internet_Computer%3F&amp;diff=229</id>
		<title>ELI5: How fast is the Internet Computer?</title>
		<link rel="alternate" type="text/html" href="https://icstaging.mywikis.net/w/index.php?title=ELI5:_How_fast_is_the_Internet_Computer%3F&amp;diff=229"/>
		<updated>2021-11-05T13:53:04Z</updated>

		<summary type="html">&lt;p&gt;Jdobbs: Adding TPS as a measurement for section 3&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;The most helpful way to way to answer this question is by choosing a vantage point.&lt;br /&gt;
&lt;br /&gt;
==1. From the point of view of an app user (what kind of dapps are possible) ==&lt;br /&gt;
&lt;br /&gt;
From the point of view of a user of a dapp, the IC is &amp;quot;fast&amp;quot; enough that app consumers would have no idea that it runs with a blockchain under the hood (or Azure or IBM or AWS). It would be comparable to centralized compute providers. This means that while it would be extremely tricky to &amp;quot;build an Airbnb web app on (traditional) smart contracts&amp;quot; because of the slow user experience, developers can create &amp;quot;Airbnb web app on the Internet Computer&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
That is how apps like OpenChat (https://www.youtube.com/watch?v=PjMIY2w480I), LinkedUp, Distrikt can provide a good user experience.&lt;br /&gt;
&lt;br /&gt;
==2. From the point of view of a dapp developer (latency of calls) ==&lt;br /&gt;
&lt;br /&gt;
There will be two relevant factors:&lt;br /&gt;
&lt;br /&gt;
a. How fast can an app READ data from a backend on the IC - Apps can make query calls to canisters (which hold state) so it can read data in less than a second (&#039;&#039;&#039;targeting under 200 milliseconds, and regularly hit under 250 milliseconds&#039;&#039;&#039;).&lt;br /&gt;
&lt;br /&gt;
b. How fast can an app WRITE data to a backend on the IC - Apps can make UPDATE calls. These go through consensus so they take more time. &#039;&#039;&#039;Target is 2 seconds&#039;&#039;&#039; currently (with constant work to decrease that further). Compared to BTC or ETH, this is orders of magnitude faster. Compared to centralized compute, this MAY seem slow at first, but actually, if you take into account the amount of replication across servers in most stacks, it is par for the course.&lt;br /&gt;
&lt;br /&gt;
Yes, currently, canisters are single-threaded... but as Dom has mentioned at events, we are working on that too.&lt;br /&gt;
&lt;br /&gt;
== 3. From the POV of blockchain measurements (Blocks per second &amp;amp; Transactions per secons) ==&lt;br /&gt;
&lt;br /&gt;
The IC is &amp;quot;unbounded&amp;quot; which means that, unlike most other protocols, it can add throughput by adding more machines. To double the calls per second... we would just add more subnets. This is a key point in what we mean by the IC being &amp;quot;unbounded.&amp;quot; At the time of this writing, it is processing &#039;&#039;&#039;25 blocks per second&#039;&#039;&#039;: https://dashboard.internetcomputer.org/&lt;br /&gt;
&lt;br /&gt;
In a recent test of the IC&#039;s throughput capacity the network clocked 300,000 (TPS) transactions per second. For comparison, Visa&#039;s payment is capable of processing 24,000 to 56,000 payment transactions per second.&lt;/div&gt;</summary>
		<author><name>Jdobbs</name></author>
	</entry>
</feed>