In the past few days, there have been more discussions surrounding @ solana 10W TPS. The reason is that @ cavemanloverboy did indeed run 100000+TPS on Solana's main website, but most people did not understand the meaning behind this data: 1) Firstly, Cavey's experiment is essentially a limit test under "ideal conditions". This means that this is not the normal performance of Solana mainnet and may differ from laboratory data in the test network environment, but the difference is not significant. Because he used a noop (no operation) null operation testing program, as the name suggests, it only performs the most basic signature verification and directly returns success without performing any calculations, changing any account status, or calling other programs. Moreover, each transaction only has 200 bytes, far below the 1kb+of normal transactions. This means that the test of 10W TPS this time was calculated in an abnormal trading environment. It tested the maximum throughput of Solana network layer and consensus layer, rather than the actual processing capacity of the application layer. 2) Another key to the success of this experiment is the Frankendancer validator client. Simply put, Frankendancer is a hybrid beta version of the Firedance validator being developed by Jump Crypto - grafting high-performance components of Firedance onto existing Solana validators. In fact, it is using Wall Street's high-frequency trading technology stack to reconstruct Solana's node system, achieving performance improvement through fine memory management, custom thread scheduling, and other underlying optimizations. But just replacing some components can achieve a 3-5 times performance improvement. 3) This test experiment shows that Solana can achieve TPS of 10w+in an ideal state, so why is there only 3000-4000 TPS in daily life? There are roughly three reasons for summarizing: 1. Solana's POH consensus mechanism requires Validators to continuously vote to maintain it, and these voting transactions alone occupy over 70% of the block space, which narrows the performance channel left for normal transactions; 2. Solana's ecological activities often involve a large number of state competition behaviors, such as when Mint releases new NFTs or MEMEs, thousands of transactions may seize the same account write permission, resulting in a relatively high proportion of failed transactions; 3. Arbitrage robots in the Solana ecosystem may send a large number of invalid transactions in order to seize MEV benefits, resulting in resource waste behavior. 4) However, the upcoming comprehensive deployment of Firedancer and Alpenglow's consensus upgrade will systematically address these issues. One of the key points of Alpenglow consensus upgrade is to transfer voting transactions off chain, which is equivalent to freeing up 70% of the space for normal transactions. At the same time, it can reduce the confirmation time to 150 milliseconds, making Solana's DEX experience infinitely close to CEX. In addition, the implementation of the local fee market can also avoid the embarrassing situation of network congestion caused by the popularity of Fomo for a single program. The benefits of FireDancer, in addition to performance optimization, are the realization of client diversity, allowing Solana to have multiple clients such as Geth Nethermand, which has a direct improvement in decentralization and single node failure, similar to Ethereum. The above. So, for those who are knowledgeable about Solana's 10W TPS discussion, it is actually a confidence in Solana's future upgraded client and consensus protocol. For those who are not knowledgeable, they try to give Solana a a sense of presence through TPS arms race (although TPS competition is outdated). However, if you understand the significance behind the experiment, you can still gain a lot. Let me explain it to you and share it with everyone.