https://bugs.documentfoundation.org/show_bug.cgi?id=151207
--- Comment #4 from Jeff Fortin Tam <[email protected]> --- > Sorry, do you really know about what are you talking about? Why attack me and question my competence for filing a bug report? > Multi-thread reprogramming it's less but a trivial task, > much worse in a project like LibreOffice with millions of lines of code. I never said this would be "trivial" nor "easy", anywhere in my bug report. I have no idea why you would think I said such a thing. By going on a limb, the closest thing I can see is where I said 'Here are some "obvious" areas where I've identified slow, single-core work', where the word "obvious" meant that the problem is easily observed (or has a very noticeable impact) in those areas of the application; not that it would be "trivial" to fix. > 100% is the four working at 100%, a 25% is usually one processor at 100% Sure. I thought my wording was clear, when I said "uses only one of your CPU cores, at 100%.", that I meant "100% of one core being used, and 0% of the others". Of course I it was not "combined" CPU usage being at 100%, otherwise I wouldn't have been filing this bug report; when you look at this in htop or gnome-system-monitor (or any CPU usage visualizer that separates the cores/threads instead of combining them), it is *very* clearly noticeable on my machine when 1 logical processor is pegged at 100% and the 7 others are sitting idle. > You have not added the information about your LibreOffice installation Oops, here it is (this was probably with version 7.4 back then, but the current 7.5.x versions, provided by Fedora 38 or via the flathub flatpak, still exhibit the issue): Version: 7.5.2.2 (X86_64) Build ID: 50(Build:2) CPU threads: 8; OS: Linux 6.2; UI render: default; VCL: gtk3 Locale: fr-CA (en_CA.UTF-8); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
