Hi Sajid - I think we all understand why an undo buffer is useful/required, my point is why keep it beyond the session we are working in? Upfront should ideally clear it when we exit the page. It's not as though we can go back to a page later and undo something we did earlier. Its usefulness is only when still in the page and as Paul indicates it isn't particularly flexible (e.g. we can't easily pick 10 or 20 undos back from a menu) and so if we ever do try and use its functionality it's incredibly slow and unwieldy.
At the same time it massively increases the database size and after prolonged sessions working on a site it makes the database so big (day after day, each time the site is worked on) it becomes a problem for all sorts of reasons - apart from the space it uses up, the particular problems I started getting was with backup, migration and/or staging with various server timeout failures from plugins and service abilities.
There seems little point in the undo buffers hanging around way beyond the current editing session, let alone for it to sill be there 24 hours later (or more sometimes as I found). Upfront needs a way of immediately clearing or limiting those to a certain number of undos.
There is also still the so far unaddressed problem of how Upfront stores all its URL data in an encoded way that makes migration and staging fail/impossible. All the well known plugins and methods I tried couldn't properly find and adjust the Upfront stored URLs because it seems Upfront has it's encoded method and so I was getting sites that got all mixed up with where they thought they were pointing for certain resources.
I understand Upfront is a massive project and these details can take time to iron out, but skimming back to my comments in this post from a year ago (Wed Mar 30 2016, 1:20:13 PM), I see I make exactly the same points and from what I understand nothing has yet changed/improved.
All in all, I still don't know if I can use or trust Upfront to cope with anything more than working on a simple live site. Again, are the undo buffer problems and the URL migration issues just something that will always be an issue because that's just how Upfront works and will always have to work because it's how the core functioning was designed and it's too late to change its working methods?