Interesting discussion from the btctalk forum.
At due time, I think the DevTeam should evaluate if this thing needs to be addressed.
Almightyruler said:
"....FST is a real resource hog. On my server the FST client consumes a whopping 3.7GB of RAM, which is by far the most of any of the clients I run. For comparison, the Bitcoin client only uses 0.6GB (although, to be fair, BTC does use much, much more disk space)
Because of the huge number of blocks a sync or rescan can take several days, at high CPU load.
I surveyed the last 500 blocks in the FST blockchain and over 96% have no additional transaction beyond the miner reward. The tradeoff for fast transactions is that the blockchain continues to grow to excess, with mostly empty blocks being issued every 12 seconds.
Some coins have toyed with limiting the block creation rate (and therefore blockchain bloat) by only permitting new blocks when a certain time period has elapsed, or there are a certain number of transactions in the mempool. So you could have a default block period of 1 or 2 minutes, EXCEPT when there's a transaction that's moving through, which will cause a more rapid block creation rate. This would greatly increase the average transaction density of each block...."
-----
(Me) While I see my own "Hog" is eating 2,1GB of Ram (down from the 3.6GB above), yes, I think here the software experts could really run a contest to find out... Who has the longest....
This is not needed here and now, but all must be addressed if you think to a long term scenario.
There are 3-4 very experts guys.... Almighty, Vampirus, Stouse and others who could make the difference, just by looking at how much interest they're putting into the discussion.