https://bugs.documentfoundation.org/show_bug.cgi?id=65046
--- Comment #31 from [email protected] --- (In reply to Kevin Suo from comment #30) > @fredgib: > So what exactly is not working at this stage? You mentioned that "What I > have witnessed is exactly what is described in the original post of this > thread". However, it was many years ago and things have changed a lot, see > bug 114159 I saw this, and like many users, I have however witnessed only one core used during processing by LibreOffice. > and > https://bugs.documentfoundation.org/showdependencytree.cgi?id=139443. This is exactly what I experience too. But it was marked as a duplicate of THIS bug, so I thought THIS bug should be marked as "major", precisely because it had been marked as "enhancement" for 7 or 8 years without being addressed in a way that forced LibreOffice to actually use all the cores. > Citing > the description of what has been reported many years ago does not help. You > should re-test with a most recent release. As I mentioned implicitly by "with all the versions since v6.0", I tested it with all the versions since 6.0, to the present version 7.2.2, with exactly the same result. > > The point is, one should clearly describe what exactly is not working today > with the multi-threading calculation in Calc, I think we are several to have done this, in https://bugs.documentfoundation.org/showdependencytree.cgi?id=139443, in this thread or in support forums (one example among several instances in several languages: https://ask.libreoffice.org/t/how-can-i-make-libreoffice-multi-threaded/18749) > and if it does not work then > one should describe which function/formula is not working, it provide clear > and simple reproducible steps. I thought any resource-intensive task would show the problem. In case I was wrong and, as you suggest, it might depend on the nature of the task, here is what I daily struggle with: 1. create a 30,000-row and two-column file with: - first column being unique integers - second column being whatever text 2. create another similar file, this time with 300,000 rows. 3. In the second file, create a third column with a formula only having a VLOOKUP to fetch the second column's value in the first file, against the first column's integer. 4. monitor your CPU resource consumption (and have a cocktail): only one core is fully used, while the other are idle. > Only in this way the devs can jump in and > help to improve. In my opinion it does not matter if new bug reports should > be opened for this purpose. I agree. Whatever works to have some skilled people solve that issue... -- You are receiving this mail because: You are the assignee for the bug.
