You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@poi.apache.org by ce...@apache.org on 2017/12/28 10:29:05 UTC
svn commit: r1819415 - in /poi/site: publish/faq.html
src/documentation/content/xdocs/faq.xml
Author: centic
Date: Thu Dec 28 10:29:05 2017
New Revision: 1819415
URL: http://svn.apache.org/viewvc?rev=1819415&view=rev
Log:
Bug 61665: Update FAQ for performance test slightly
Modified:
poi/site/publish/faq.html
poi/site/src/documentation/content/xdocs/faq.xml
Modified: poi/site/publish/faq.html
URL: http://svn.apache.org/viewvc/poi/site/publish/faq.html?rev=1819415&r1=1819414&r2=1819415&view=diff
==============================================================================
--- poi/site/publish/faq.html (original)
+++ poi/site/publish/faq.html Thu Dec 28 10:29:05 2017
@@ -797,7 +797,7 @@ System.out.println("POI Scratchpad came
<p>(If you're here, you probably think it's Apache POI. However, it
often isn't! A moderate laptop, with a decent but not excessive heap
- size, from a standing start, can normally read or write a file with
+ size, from a standing start, can normally read or write a file with
100 columns and 100,000 rows in under a couple of seconds, including
the time to start the JVM).</p>
@@ -809,22 +809,22 @@ System.out.println("POI Scratchpad came
Run SSPerformanceTest with arguments of the writing type (HSSF, XSSF
or SXSSF), the number rows, the number of columns, and if the file
should be saved. If you can't run that with 50,000 rows and 50 columns
- in HSSF and SXSSF in under 3 seconds, and XSSF in under 10 seconds
+ in HSSF and SXSSF in under 3 seconds, and XSSF in under 20 seconds
(and ideally all 3 in less than that!), then the problem is with
your environment.</p>
<p>Next, use the example program
<a href="https://svn.apache.org/repos/asf/poi/trunk/src/examples/src/org/apache/poi/ss/examples/ToCSV.java">ToCSV</a>
(<a href="https://svn.apache.org/viewvc/poi/trunk/src/examples/src/org/apache/poi/ss/examples/ToCSV.java">viewvc</a>)
- to try reading the a file in with HSSF or XSSF. Related is
+ to try reading the file in with HSSF or XSSF. Related is
<a href="https://svn.apache.org/repos/asf/poi/trunk/src/examples/src/org/apache/poi/xssf/eventusermodel/XLSX2CSV.java">XLSX2CSV</a>
(<a href="https://svn.apache.org/viewvc/poi/trunk/src/examples/src/org/apache/poi/xssf/eventusermodel/XLSX2CSV.java">viewvc</a>),
which uses SAX parsing for .xlsx. Run this against both your problem file,
and a simple one generated by SSPerformanceTest of the same size. If this is
slow, then there could be an Apache POI problem with how the file is being
processed (POI makes some assumptions that might not always be right on all
- files). If these tests are fast, then any performance problems are in your
- code!</p>
+ files). If these tests are fast, then performance problems likely are in your
+ code.</p>
<a name="faq-N10192"></a>
<div class="h4">
Modified: poi/site/src/documentation/content/xdocs/faq.xml
URL: http://svn.apache.org/viewvc/poi/site/src/documentation/content/xdocs/faq.xml?rev=1819415&r1=1819414&r2=1819415&view=diff
==============================================================================
--- poi/site/src/documentation/content/xdocs/faq.xml (original)
+++ poi/site/src/documentation/content/xdocs/faq.xml Thu Dec 28 10:29:05 2017
@@ -367,7 +367,7 @@ System.out.println("POI Scratchpad came
Or Apache POI?</p>
<p>(If you're here, you probably think it's Apache POI. However, it
often isn't! A moderate laptop, with a decent but not excessive heap
- size, from a standing start, can normally read or write a file with
+ size, from a standing start, can normally read or write a file with
100 columns and 100,000 rows in under a couple of seconds, including
the time to start the JVM).</p>
<p>Apache POI ships with a few programs and a few example programs,
@@ -378,21 +378,21 @@ System.out.println("POI Scratchpad came
Run SSPerformanceTest with arguments of the writing type (HSSF, XSSF
or SXSSF), the number rows, the number of columns, and if the file
should be saved. If you can't run that with 50,000 rows and 50 columns
- in HSSF and SXSSF in under 3 seconds, and XSSF in under 10 seconds
+ in HSSF and SXSSF in under 3 seconds, and XSSF in under 20 seconds
(and ideally all 3 in less than that!), then the problem is with
your environment.</p>
<p>Next, use the example program
<link href="https://svn.apache.org/repos/asf/poi/trunk/src/examples/src/org/apache/poi/ss/examples/ToCSV.java">ToCSV</link>
(<link href="https://svn.apache.org/viewvc/poi/trunk/src/examples/src/org/apache/poi/ss/examples/ToCSV.java">viewvc</link>)
- to try reading the a file in with HSSF or XSSF. Related is
+ to try reading the file in with HSSF or XSSF. Related is
<link href="https://svn.apache.org/repos/asf/poi/trunk/src/examples/src/org/apache/poi/xssf/eventusermodel/XLSX2CSV.java">XLSX2CSV</link>
(<link href="https://svn.apache.org/viewvc/poi/trunk/src/examples/src/org/apache/poi/xssf/eventusermodel/XLSX2CSV.java">viewvc</link>),
which uses SAX parsing for .xlsx. Run this against both your problem file,
and a simple one generated by SSPerformanceTest of the same size. If this is
slow, then there could be an Apache POI problem with how the file is being
processed (POI makes some assumptions that might not always be right on all
- files). If these tests are fast, then any performance problems are in your
- code!</p>
+ files). If these tests are fast, then performance problems likely are in your
+ code.</p>
</answer>
</faq>
<faq>
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@poi.apache.org
For additional commands, e-mail: commits-help@poi.apache.org