In article <1300785359.7641.12.camel@duiker>, John-Mark Bell <j...@netsurf-browser.org> wrote:
[snip] > > > > > Remove the -v flag. That is what enables verbose logging. Note > > > that this simply stops NetSurf formatting and emitting the log data. > > > It will still involve checking "do I need to log this?" > > > > Thanks, Rob. I also removed the -v flag, without putting an | anywhere. > Commenting out bits of the !Run file using | is pretty much guaranteed > to end in tears. Please don't do this. OK, I won't, in future. It was a kind of one off thing. > Additionally, disabling logging totally defeats the point of us asking > for log files when you report a bug. I realised that, thanks, but wanted to see if logging had any significant effect on file loading and rendering. Equally, if it had worked logging could also be turned back on again in extremis. > > NetSurf seemed to be entirely stable in both cases. As far as I could > > tell, there was no discernible, subjective change in time in loading > > and rendering files, in either case. > It would be; logging simply isn't a significant proportion of runtime. > NetSurf spends the vast majority of its time doing the things you'd > expect (namely, fetching and rendering web pages). Yes, I now realise! > > I guess that I must accept that my machine /is/ rather slow. But, as I > > am retired I can make endless cups of tea whilst things happen. 8-) > I'm not sure you've told us what your machine is or what led you to > believe that turning off logging would help. An A7000+. I didn't believe anything at all really, I just wanted to know. A bit like mt Everest I suppose, because it was there! Um, I am unlikely to replace my machine until hell freezes over and I just wondered if it could be provoked into making NetSurf a smidgion faster. Brian
