If the royal food taster goes corrupt, you need to create a new one
Ok got it; I had a performance test that appears superficially to contradict this; and my problem was that my test model was wastefully keeping a transaction history in memory that was never being queried. This resulted in a linear growth of model size in memory, resulting in a long clone times. (That's my theory) going to remove the transaction table from memory, ... that can always be recreated by replaying all the messages (wow.. that's incredible! ) ...and that should = a test that proves how it all works. If this works, I'd like to offer it for consideration as sample code for the docs?
so far, it looks like the sample code is thin on 'best practice' examples, or examples that show with tests, why (and when) you'd choose A over B.
working on a small accounts demo.
awesome, appreciate the love
are there any open source projects or other samples that I can look at to glean some best practices; I'm quite in the dark and guessing, and writing very rudimentary tests, quite a slow process.