Requesting ability to clear internal buffers safely. Currently have to use 13000 element max

[ghowland]

Problem: I have too many elements. Currently my max is set to 13000, and doing that increased my RAM on my app by 250MB.

I have basically a data browser, and it creates the UI from the data, and so there is a lot of UI space. I switched to only using ints to see if it conserved your internals, but it didn't.

I need something where I can:

• clear all the current element buffers, so that I can switch to a new set of data.
• totally de-init clay and restart it again. Currently it doesn't work properly with multiple initializations

I dont care if I lose element tracking at that transition point, because all the UI is changing then anyway.

My current workflow works with 13000, but I can see it going much higher as these are unique elements out of a database, and databases are arbitrarily large.

Obviously "use less" is good advice, but it goes against the design I made, and I didn't think tracking 10k ints would cost me much. I think it would be good to at least be able to turn it off and back on again.

[ghowland]

Here's a video so you can see it happen: https://youtu.be/S9B-lbkXgOE

Order:

• Nav to text field, enter text
• Change pages, this new page is broken and I cant edit the text because the max elements hit (13000 wasnt enough after all)
• Back to first page, can delete the added text
• Jump to 3rd page, can edit text
• Back to 2nd page, cant edit text because I went to this page after I maxed out the elements

Clearly, there arent 13000 elements being shown in the video, but thats the problem with accumulation, because any of my elements could be rendered on any page, thats the nature of the data browser I designed.

Workaround is just add more max elements. I could also change the ID numbering strategy to try to re-use numbers, but now the data can't be rendered arbitrarily because it could collide. So that's the problem with not being able to reset. In a standard system, I wouldnt need 13000 elements, but in a database driven system, I need more than that to uniquely name and dynamically render them.