I would argue you dont actually want to insert/remove from both buffer. Insertion and deletion are both some modifications and modifying the current working set is exactly what we tried to avoid! Instead i would formulate it like so: you operate only current data, insert and remove as you please bur at the end of some period you copy everything (or synchronize in some other way) into the old buffer from where it may be safely read without worry of things changing
🎉
I would argue you dont actually want to insert/remove from both buffer. Insertion and deletion are both some modifications and modifying the current working set is exactly what we tried to avoid! Instead i would formulate it like so: you operate only current data, insert and remove as you please bur at the end of some period you copy everything (or synchronize in some other way) into the old buffer from where it may be safely read without worry of things changing
Fair point, I’m working on the assumption that no inserts will occur during updates, which won’t hold in all cases
you mean combining Mysql with the Python or C++ ?
Is it v-sync’ed or is something up with performance?
Something is indeed up with performance, a mesh of a million points probably shouldn’t be updated naively. 🤣