Hi Ben,
Thanks for the explanation, it makes sense and we’d really like to see the new mass createRows feature so our more advanced scenarios will work faster.
In the meantime do you have any suggestions for a workaround we can use until the new method? Is there someway of “disabling” the render logic after each row. I vaguely recall something Zach posted somewhere about “disconnecting” a model from its component and then reattaching it? Perhaps I can redesign the page and models to perform the required mass creates on an isolated model and then directly copy or move the data to the real “display” model?
Just to prove you’re right and one workaround option that might be available in some scenarios is to not have any component bound to the model so no rendering occurs. You do in fact get the expected linear performance:
Created rows: 1 in 0.011s = 0.011s per row Created rows: 10 in 0.043s = 0.0043s per row<br>Created rows: 100 in 0.389s = 0.00389s per row<br>Created rows: 200 in 0.705s = 0.003525s per row<br>Created rows: 500 in 1.731s = 0.00346s per row<br>Created rows: 1000 in 3.58s = 0.00358s per row
Cheers,
Stephen
