Summary: | [SAMPLE] Areas where multithreading would be needed to improve slow performance of common tasks in huge (million rows) spreadsheets | ||
---|---|---|---|
Product: | LibreOffice | Reporter: | Jeff Fortin Tam <nekohayo> |
Component: | Calc | Assignee: | Not Assigned <libreoffice-bugs> |
Status: | UNCONFIRMED --- | ||
Severity: | enhancement | CC: | aron.budea, miguelangelrv |
Priority: | medium | Keywords: | perf |
Version: | unspecified | ||
Hardware: | All | ||
OS: | All | ||
See Also: |
https://bugs.documentfoundation.org/show_bug.cgi?id=151206 https://bugs.documentfoundation.org/show_bug.cgi?id=154525 |
||
Whiteboard: | |||
Crash report or crash signature: | Regression By: | ||
Bug Depends on: | |||
Bug Blocks: | 114159, 136524, 139443 |
Description
Jeff Fortin Tam
2022-09-27 21:45:35 UTC
For calc it is active several versions ago. With a calc spreadsheet open. Menu/Tools/Options/LibreOffice Calc/Calculate - CPU Threading Settings That setting* is already enabled on my end, so visibly it is not working/implemented for the usecases I have benchmarked above. *: I don't even see why there is a setting for this, it should always be enabled by default for everyone. It's like having a setting for "Allow my Lamborghini to go faster than 20 km/h" or "Don't make me wait to see the doctor when they already are available" :) Don't set up your own report as NEW, except you assign it to you, to resolve it. Sorry, do you really know about what are you talking about? Multi-thread reprogramming it's less but a trivial task, much worse in a project like LibreOffice with millions of lines of code. Are you sure that all the described operations are susceptibles to convert to multi-thread. On my windows with 4 logical processors, on the task manager, 100% is the four working at 100%, a 25% is usually one processor at 100% You have not added the information about your LibreOffice installation, Menu/Help/About LibreOffice (Use the button in middle to copy). > 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 I think so.When processing hundreds of pages of Word, libreOffice is also slower to open than the competition, and we all want LibreOffice to be better |