Bug Hunting Session
Bug 48552 - Slow to process "VLOOKUP" formula
Summary: Slow to process "VLOOKUP" formula
Status: RESOLVED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
3.5.2 release
Hardware: x86-64 (AMD64) All
: medium critical
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: perf
Depends on:
Blocks: Calc-Function
  Show dependency treegraph
 
Reported: 2012-04-11 05:16 UTC by Rui Simoes
Modified: 2018-05-22 07:13 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:


Attachments
slow in formula "procv" (1.21 MB, application/vnd.oasis.opendocument.spreadsheet)
2012-04-11 05:16 UTC, Rui Simoes
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Rui Simoes 2012-04-11 05:16:59 UTC
Created attachment 59803 [details]
slow in formula "procv"

When i create a comparation between 2 sheets and use the formula "procv", the libreoffice calc hangs for a long time.

When i open the same file in "Microsoft Office" is 85% more fast.

Try with the file I sent in attach, take a look in the sheet "Analise".

Thanks
Comment 1 bfoman (inactive) 2012-08-31 13:06:02 UTC
Confirmed with:
LO 3.5.6.2 
Build ID: own W7 debug build
Windows 7 Professional SP1 64 bit

Very slow opening of the file, stuck for minutes at Adapt Row Height.
Comment 2 Rui Simoes 2012-08-31 13:20:32 UTC
With LO 3.6.1 the problem is the same.
Comment 3 vlb 2012-09-18 14:36:14 UTC
I can confirm this.
I have too a file what is very slow in the calculation in the sheet and hangs by calculation, when i change a cel in calc. I have check it in excel and there was no problem.
The sheet have different formulas.

LO 3.6.1.2 windows 7 professional 64 bits
Comment 4 bfoman (inactive) 2012-10-11 12:50:23 UTC
NEW per comment 3.
Comment 5 QA Administrators 2015-01-05 17:52:24 UTC Comment hidden (obsolete)
Comment 6 Rui Simoes 2015-01-06 10:19:27 UTC
Now i'm using Version 4.4.0.1 pt_PT, Windows and Linux, and the problem continuous.

Windows 7 Sp1 x64 pt_PT

Linux Ubuntu 14.04LTS 64bits
Comment 7 Björn Michaelsen 2015-11-21 11:23:48 UTC
(component calc)
Comment 8 QA Administrators 2017-11-28 08:39:29 UTC Comment hidden (obsolete)
Comment 9 Winfried Donkers (retired) 2018-05-22 06:26:41 UTC
Changed the locale function name PROCV to the default English function name.

Opening attachment 59803 [details] on a 6 year old Windows machine (with Windows 10) with LibreOffice version 5.4.7 takes about 6 seconds, which IMO is not very slow given the almost 26000 calls to VLOOKUP.
Opening  attachment 59803 [details] on an 8 year old Linux machine (with openSUSE Leap15) with LibreOffice version 6.0.4 takes about 6 seconds too.

Since reporting this bug some fundamental improvements in the efficiency of Calc have been implemented.

@Rui Simoes: Do you still experience extreme slow opening of attachment 59803 [details] when using a recent version of LibreOffice (i.e 5.4 or 6.0)?
Comment 10 Rui Simoes 2018-05-22 06:36:14 UTC
(In reply to Winfried Donkers from comment #9)
> Changed the locale function name PROCV to the default English function name.
> 
> Opening attachment 59803 [details] on a 6 year old Windows machine (with
> Windows 10) with LibreOffice version 5.4.7 takes about 6 seconds, which IMO
> is not very slow given the almost 26000 calls to VLOOKUP.
> Opening  attachment 59803 [details] on an 8 year old Linux machine (with
> openSUSE Leap15) with LibreOffice version 6.0.4 takes about 6 seconds too.
> 
> Since reporting this bug some fundamental improvements in the efficiency of
> Calc have been implemented.
> 
> @Rui Simoes: Do you still experience extreme slow opening of attachment
> 59803 [details] when using a recent version of LibreOffice (i.e 5.4 or 6.0)?


I'm using now the 6.0.4 version and de VLOOKUP formula runs like expected with no problem.
Comment 11 Winfried Donkers (retired) 2018-05-22 07:13:35 UTC
(In reply to Rui Simoes from comment #10)
 
> I'm using now the 6.0.4 version and de VLOOKUP formula runs like expected
> with no problem.

Thank you for your feedback.
OK, I will set this bug report to RESOLVED/WORKSFORME.