best practices - store huge data

[Vortico (VCV - Andrew)]

Yes, that’s fine. When the user hits Delete on a module, the Module is deleted on the UI thread after it’s removed from the Engine.

Make sure to use std::launch::async with std::async so a new thread is launched, not std::launch::deferred which runs the code on the thread that requests the task’s result.

[q8fuel]

@GretchenV

Furthermore, saveThread in the example code happily existed on the stack but if you make it a member variable so you can join in the destructor, you must also protect yourself against the case where the class instance is destroyed without the thread being created at all or where autoSaveTriggered is called when a thread has already been created in a previous invocation.

Done, thanks!

@GretchenV

Yes, a saveThread.join() in the destructor is a good idea. But also, you need to make sure no other thread is modifying controlData and the data array it references while the saveThread is running, otherwise what you are you saving?

That’s a bit more tricky. What would you suggest for this? A sort of ring buffer?

[chaircrusher]

One thing I know you can do for saving to Json is compress it & then base64 encode it. Then you have text you can store in Json as a string. It’ll still be big but not that big.