It will be interesting to see if this stress test brings about a solution to the block size problem. Hopefully we can find a solution to ensure that the blockchain continues to function without any issues or unnecessary delays.
This test isn't really going to change anything, or bring any solutions... This is only raising awareness of a problem we already know we have, it isn't proposing anything new. It's an interesting test, but with a predictable outcome for which the solution is already in discussion for quite some time, and there is already code ready to be deployed that helps prevent a situation like this.
Yes, the test is meaningless - it's an annoyance aiming at price manipulation.
The solution to stop spam attacks like this is certainly not a max_blocksize increase, because even at 20x times the blocksize the resources needed to perform such an attack are still extremely small for any serious attacker.
The practical solution for now is: Prioritize your transaction by sending it with an adequate fee.
The general solution is: Increase fees for spam transactions, i.e. fees should rise non-linearly (maybe exponentially) for small-value transactions with big data size.
ya.ya.yo!
