Bug 34789 - Standart filter works very slow
Summary: Standart filter works very slow
Status: RESOLVED FIXED
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
3.3.1 release
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-02-26 23:49 UTC by sorath
Modified: 2011-02-28 02:08 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments
example file to demonstrate slow filter (262.47 KB, application/vnd.oasis.opendocument.spreadsheet)
2011-02-26 23:49 UTC, sorath
Details

Note You need to log in before you can comment on or make changes to this bug.
Description sorath 2011-02-26 23:49:43 UTC
Created attachment 43867 [details]
example file to demonstrate slow filter

If table contains thousands of string then standart filter works to very slow in LibreOffice-3.3.0 and LibreOffice-3.3.1.
(this bug was tested by me on linux-x86-64, but it's need to verify on other os)


1. Open attached file "qwedasr.ods" (this file was sent me by another man) 
2. choose second row "val" and aplay "standart filter" (Data -> Filter -> Standart Filter) by setting [val < -500]. Note that it takes about few seconds (on my system it's about 3 seconds [amd phenom II X4 955 (3.2 GHz), 4GB ram]).
3. Now (or you can do it first instead of item 2 of descrition) select the same row "val" and aplay "standart filter" (Data -> Filter -> Standart Filter) by setting [val > -100]. Note that time of filtering takes few second again (on my system it's about 7-10 sec.).

Such time results are very strange as in OpenOffice-3.2.1 and -3.3.0 such filtering works instantly.

testing system configuration:
Linux 2.6.36-gentoo-r5 x86_64 
AMD Phenom(tm) II X4 955 Processor
4 Gb RAM

installed versions: 
app-office/libreoffice-bin-3.3.0(-r1)
app-office/libreoffice-bin-3.3.1
Comment 1 Cédric Bosdonnat 2011-02-28 02:08:27 UTC
I can reproduce this in 3.3.1 build, but not in master build. This will be fixed in 3.4.