I've trained myself to cease using the save function in Writer in order to attain 95.2% availability for editing when the UI is not frozen still, with a 10 minute autosave set. My encyclopaedia is 433 pages and 71k words. Saving takes 29 seconds. So I don't use save anymore. I just tried cranking autosave to 1 minute and now I can only work on the file for 31 seconds each minute or 51.7% of the time and the other 29 seconds the screen is froze and going pale while autosaving. It was set at 10 minutes before which makes me realise why it felt sluggish lately. It only works 95.2% of the time at 10 minutes, because autosave locks up the GUI and i can no longer even scroll about the file. PROPOSED SOLUTION 1. Cease setting and using file locking / mutex protection when autosaving (not save). The UI is now not locked and users will notice it immediately faster. Autosave can go to 1 minute. YES this is unsafe and leads to corrupt file and wasted CPU. But that's OK due to... 2. Monitor the keyboard and mouse for any keystrokes, and interupt the background autosaving thread or global signal to cancel any running **29 second** autosave operations (not proper File... Save) as soon as the user begins intercting again that (eventually hopefully) stops the autosave thread inside of **1 second** so deep inside a huge loop I guess a whole bunch of if() statements to check if user is present. Meanings, if the user begins typing and changing the file (actually even just scrolling is blocked during autosave). 3. IF the autosave completes before the user touches keyboard/mouse again, but the user THEN hits File... Save, the optimisation will MOVE the autosaved file into the main file instantly saving it (will take 10 milliseconds) which will blow the users mind a little bit and make the app responsive 99.999% of time she use it. FEELS VERY FASTER He needs to see a flashing cursor, not a pale white screen every 31 seconds (like I have it presently for laffs). I will go and change mine now to 12 minutes I think. Then I can edit my book 11.5 minutes out of each 12 minute when I work. CAN SOMEONE PLEASE SUGGEST ME A PROFILING TOOL? I'm curious to see which function is involved in this 29 second save on 4.2Ghz Ryzen 32GB workstation. Startup time is 0.2 seconds. real 0m0.201s user 0m0.134s sys 0m0.098s Loading of document time is 19.7 seconds. time libreoffice /home/tom/Dropbox/Astonishing-Evidence-of-Life/An-Astonishing-MASTER.odt real 0m19.713s user 0m18.744s sys 0m1.079s
Please attach the file, sanitised, if needed: https://wiki.documentfoundation.org/QA/Bugzilla/Sanitizing_Files_Before_Submission
The request for saving in the background is bug 48416
(In reply to Buovjaga from comment #2) > The request for saving in the background is bug 48416 Thank you. I would love to upload, but I am too precious about me dumb copyrights and people stealing my lucrative ideas. Truth be told you guys are probably quite honorable and wouldn't do that. A tool that would encrypt all the text would do, then you would have some cool UFO pics left over. 136 MB file. Plus it's about Aliens and UFO's so it goes with the territory to be unreasonably paranoid about matters that, in reality, should be openly discussed (E.T.). I'll dupe out a dated copy now and drop it up here in 4 years from now. Check back here October 2028 if Earth is still here (half joking but I did set a google calendar for it!). By then it should be in print and less valuable to 'youknowwhat.
(In reply to Tom Atkinson from comment #3) > (In reply to Buovjaga from comment #2) > > The request for saving in the background is bug 48416 > > Thank you. > > I would love to upload, but I am too precious about me dumb copyrights and > people stealing my lucrative ideas. Truth be told you guys are probably > quite honorable and wouldn't do that. A tool that would encrypt all the text > would do, then you would have some cool UFO pics left over. 136 MB file. > > Plus it's about Aliens and UFO's so it goes with the territory to be > unreasonably paranoid about matters that, in reality, should be openly > discussed (E.T.). > > I'll dupe out a dated copy now and drop it up here in 4 years from now. > Check back here October 2028 if Earth is still here (half joking but I did > set a google calendar for it!). By then it should be in print and less > valuable to 'youknowwhat. After sanitising the document, it will be illegible, so there is no danger of copyright infringement.