Bug 85096 - Poor calc performance with big files
Summary: Poor calc performance with big files
Status: RESOLVED DUPLICATE of bug 36779
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
4.3.2.2 release
Hardware: Other Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-10-16 14:57 UTC by erno rubbik
Modified: 2014-10-16 20:21 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description erno rubbik 2014-10-16 14:57:32 UTC
Hello

When dealing with big files, Calc is very sluggish and tend to hog all the system ressources. Increasing memory settings do not help, neither using ods

LO performance exponentially drops as file size increases, the attached file loads fast but takes ages to render and edit, takes about 700MB+ in system memory, and crashes on save with "bad allocation" error (system has 4GB of free RAM) 

The same file suffer no performance issue and takes only 88MB when opened with M$ Office on the same system

I read somewhere you need files to debug, here is a big one

I hope this will help to pinhole the overall calc perf issue


Thank you so much already
Comment 1 erno rubbik 2014-10-16 15:06:40 UTC
could not attach the too big file link here : 
http://www.ovive.fr/sugarcrm/testfile.zip
Comment 2 tommy27 2014-10-16 18:12:57 UTC
please give details about the exact version of your O/S

I can confirm issue under Win7x64 using LibO 4.3.2.2 and 4.4.0.0.alpha0+
Build ID: 2d6dacc1c93bfd4a9086f8fde6b0edbfdeb573c9
TinderBox: Win-x86@42, Branch:master, Time: 2014-10-13_23:44:09

Calc freeze loading that file. status NEW.
Comment 3 tommy27 2014-10-16 18:14:50 UTC
Excel viewer is slow too but not as LibO dealing with that .xls
Comment 4 m_a_riosv 2014-10-16 20:21:06 UTC
I think this is a duplicate of: https://bugs.freedesktop.org/show_bug.cgi?id=36779

Please if you are not agree, reopen it.

*** This bug has been marked as a duplicate of bug 36779 ***