<html>
<head>
<base href="https://bugs.documentfoundation.org/">
</head>
<body><span class="vcard"><a class="email" href="mailto:michael.meeks@collabora.com" title="Michael Meeks <michael.meeks@collabora.com>"> <span class="fn">Michael Meeks</span></a>
</span> changed
<a class="bz_bug_link
bz_status_NEW "
title="NEW - Thread the Calc CSV parser"
href="https://bugs.documentfoundation.org/show_bug.cgi?id=124982">bug 124982</a>
<br>
<table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>What</th>
<th>Removed</th>
<th>Added</th>
</tr>
<tr>
<td style="text-align:right;">Severity</td>
<td>normal
</td>
<td>enhancement
</td>
</tr>
<tr>
<td style="text-align:right;">Ever confirmed</td>
<td>
</td>
<td>1
</td>
</tr>
<tr>
<td style="text-align:right;">Summary</td>
<td>Calc seems only capable of using one CPU core
</td>
<td>Thread the Calc CSV parser
</td>
</tr>
<tr>
<td style="text-align:right;">Status</td>
<td>UNCONFIRMED
</td>
<td>NEW
</td>
</tr>
<tr>
<td style="text-align:right;">CC</td>
<td>
</td>
<td>libreoffice@kohei.us
</td>
</tr></table>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - Thread the Calc CSV parser"
href="https://bugs.documentfoundation.org/show_bug.cgi?id=124982#c5">Comment # 5</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - Thread the Calc CSV parser"
href="https://bugs.documentfoundation.org/show_bug.cgi?id=124982">bug 124982</a>
from <span class="vcard"><a class="email" href="mailto:michael.meeks@collabora.com" title="Michael Meeks <michael.meeks@collabora.com>"> <span class="fn">Michael Meeks</span></a>
</span></b>
<pre>Calc has a single threaded CSV parser - that is correct. Given the general
simplicity of the CSV file format, it seems likely that profiling that with
kcachegrind and optimizing it further would probably yield more of a win than
trying to thread it - but of course, its possible that a parse/insert
separation would be helpful.
It is also possible that some column iterators for data insertion might help
optimize the mdds side.
Can you paste a few rows of your CSV file ? how homogeneous is it ? are there
large gaps in lots of the columns - or is it uniform ?
Anyhow - an enhancement here - someone might like to hack on that:
sc/source/filter/orcus/orcusfiltersimpl.cxx
bool ScOrcusFiltersImpl::importCSV(ScDocument& rDoc, SfxMedium& rMedium) const
Looks like a good place to poke. I believe much of the CSV parsing is inside
the standalone orcus library which should be easy to hack on - but whether
that's where the slowness is its hard to say without profiling =)
HTH.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>