TRC: Optimize transactionHistoryStore occupancy space #41
This doc describes the solution of optimizing transactionHistoryStore occupancy space
In current storage model, transaction result saves in transaction history store and it occupies the most space.
TRON database already occupied 163GB and it increases 20G each month. So how to optimize space is very import.
TransactionHistory doesn't directly save in transactionHistoryStore after the execution of transactions.
Add transaction history in memory and save in disk after executing one whole block.
Saving transaction history for a whole block could reduce duplicate data and protocol buffer compression is more effective for large data.
There are no backwards compatibility concerns.