Bug Hunting Session
Bug 54318 - : Working slow on large spreadsheets w/ Vlookup inserted ( file size = 13+Mb )
Summary: : Working slow on large spreadsheets w/ Vlookup inserted ( file size = 13+Mb )
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
(earliest affected) release
Hardware: Other All
: high major
Assignee: Not Assigned
Whiteboard: BSA
Depends on:
Reported: 2012-08-31 11:54 UTC by Gyorgy Zold
Modified: 2013-06-27 23:59 UTC (History)
4 users (show)

See Also:
Crash report or crash signature:


Note You need to log in before you can comment on or make changes to this bug.
Description Gyorgy Zold 2012-08-31 11:54:06 UTC
Problem description: 

Steps to reproduce:
1.Create a spreadsheet (sheet 1) w/ 60k rows,20 coloumns
Fill up with data
2.create a new spreasheet ( sheet 2 )w/ 15k rows, 20 coloumns ( first coloumn filled up w/ data )
populate the cells of coloumn 2 to 20 via vlookup function, looking for data in the sheet 1

Current behavior: 
- takes up long time ( 30 min - couple of hours ), 
- takes up to 4 Gb Ram
- uses only 1 core of 8 within the CPU

Expected behavior: max 3 min processing time , more cores in parallel ( as MS Excell does! )

Platform (if different from the browser): 
Browser: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:15.0) Gecko/20100101 Firefox/15.0
Comment 1 AZlinux 2013-04-04 07:22:51 UTC
Confirmed in:
Ubuntu 12.04
Build ID: 350m1(Build:2)

It is a feature that greatly limits the possible migration of Excel to Calc.
Comment 2 Joel Madero 2013-06-26 03:47:39 UTC
Kohei or Markus - thoughts on this one? I believe there are already bugs out there that say things like "support more than one core" -> is this really actionable? IMO we should close as it's a big request that isn't specific to vlookup (vlookup might just be a symptom of not supporting more than one core)
Comment 3 Joel Madero 2013-06-27 23:59:44 UTC
Closing this, I have talked to our two spreadsheet experts and what I put in comment is indeed true. This is not actionable and the grand scheme of "use all cores" is incredibly difficult - maybe long term planning but the particular bug won't be useful in implementing it.

Thanks for the report.