铭文狂热传至Layer2 zkSync为何能通过天量交易压力测试？

The short-term influx of massive transactions from the author's encrypted observer source engraved on the chain is indeed a stress test of the performance of the public chain, but the result is not downtime. On the contrary, it is an open training. The result is that the peak stability and so on have all stood the test perfectly. Is it a bit counterintuitive at first glance? Next, I will clarify the working principle of packaging out blocks with technical logic. Simply put, users construct the sorting sequence of transactions, then package them into blocks according to the high and low ranking, and then pass them into blocks. System verification finally goes to the main network to complete the status confirmation. There is a key point here, which is easy to create the illusion of bad experience. Most users will send the transaction through the wallet by waiting for the wallet to initiate the transaction. The transaction will first enter the remote call server and then receive these transactions into the queuing sequence. The queuing time here is short, ranging from a few seconds to a few minutes. If people wait for a long time, they will think that the transaction has failed, and then the front end will return the prompt of transaction failure. However, this is not the case. It means that the transaction really failed, but only because the response time and feedback logic are incompatible with the queuing and packaging transaction logic. This is exactly why some transactions that clearly show failure are displayed and succeeded by the back-end server after waiting for a period of time. If the user directly uses the back-end code call without taking the wallet pipeline, there will be no problem that the response time is overtime and the failure is prompted. The experience will be relatively smooth, which will indeed be obtained by some scientists who can use the back-end code instructions. The problem that has the advantage but essentially belongs to the wallet experience end has nothing to do with the processing capacity of the chain. When the user sends a transaction to the queue for a short time, each transaction will be superimposed from the value. If the last transaction is still in the queue state, the user will allocate these transactions according to the data and then sort them in order. However, if the user sees that the last transaction failed in the previous paragraph and submits a new transaction at the same time, it is likely that the new transaction will be submitted due to the wallet end and. The problem of interface call is that some transactions are not successfully submitted to the queuing sequence in the end. Users think that many transactions have actually been submitted, but as long as they receive them, they will sort them out. In this way, the behavior of constantly submitting new transactions when users see the feedback transaction failure will also cause a large number of transactions to fail, because there is no submission to the back end of the chain at all, but you think that you have submitted a lot of transactions at the front end. On the whole, the logic problem of wallet response time and the user's anxiety are superimposed on the chain. The transaction behavior will cause a lot of transaction failures. If the background transaction processing workflow is clear, it is relatively easy to avoid these optimization experience problems. Based on the above popular science, let's clarify that the downtime problem chain is not down. It's just the display problem of the browser front end, because the browser will pull the latest data through the interface, but the interface response will be delayed. A lot of new transactions will slow down the response. In short, the synchronization speed of the browser's pull data can't keep up with the surge of queued transactions. This is the browser front end. The problem has nothing to do with the operation of the chain. Usually, when the transaction speed slows down properly and the browser can grab new data, the problem will be solved. When the browser is not available, it can be cross-verified by other browsers that synchronize the block data information. For example, what is the operation performance of the real chain? After the so-called downtime rumor broke out, the official staff frequently sent out refreshing news on Twitter, which actually reached the peak. Under normal circumstances, there are only about two, which shows that a large number of new transactions have actually resisted. Stress: This has indeed given thousands or even tens of thousands of people a full stress test in the future. The special mechanism determines that the greater the transaction volume, the cheaper the fee will be. In fact, the fee is indeed cheaper, because the transaction cost is also shared. According to the data, the average value of the last hour has also decreased. Everyone's experience may be different, but the running data of the integrated chain is indeed cheaper, which proves that the smoother experience needs to upgrade the existing user scale by an order of magnitude. According to the inscription on the data, a new transaction has been cast for hours, and as mentioned above, the government has already known about the stress test activity initiated by the community and taken urgent measures to ensure the orderly progress of the chain. This data is indeed a good stress test experiment for me, and its positive impact is greater than its negative impact. In the long run, the inscription event did not return the performance to the prototype as rumored, but provided practical experience for further performance optimization, but it was lifted according to me. There are other inscriptions being cast, which are not as good as that, but also add a fire to this stress test. On the whole, the results are good. If you clarify the technical logic of sorting out blocks in the background and then get rid of the bad experience and misunderstanding, you should know that everything is running well. We have to give more confidence. 比特币今日价格行情网_okx交易所app_永续合约_比特币怎么买卖交易_虚拟币交易所平台

注册有任何问题请添加 微信：MVIP619 拉你进入群

文章转载注明 网址：https://netpsp.com/?id=62296