<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Apache POI on Jaehyun&#39;s Blog</title>
    <link>https://hongjae.pages.dev/en/tags/apache-poi/</link>
    <description>Recent content in Apache POI on Jaehyun&#39;s Blog</description>
    <image>
      <title>Jaehyun&#39;s Blog</title>
      <url>https://pub-8eb6fdee382f4b0390e652016dc5f15a.r2.dev/og-image.jpg</url>
      <link>https://pub-8eb6fdee382f4b0390e652016dc5f15a.r2.dev/og-image.jpg</link>
    </image>
    <generator>Hugo -- 0.118.2</generator>
    <language>en</language>
    <lastBuildDate>Fri, 14 Jul 2023 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://hongjae.pages.dev/en/tags/apache-poi/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Fixing Memory Issues in Large Excel Export and Import with Apache POI SXSSF</title>
      <link>https://hongjae.pages.dev/en/posts/230714_apache_poi_sxssf_large_excel/</link>
      <pubDate>Fri, 14 Jul 2023 00:00:00 +0000</pubDate>
      <guid>https://hongjae.pages.dev/en/posts/230714_apache_poi_sxssf_large_excel/</guid>
      <description>When building admin or B2B back-office systems, Excel download and upload are pretty much required features.
In Java, Apache POI is the standard library, and at first I just implemented it with XSSFWorkbook without thinking too much.
On local with a few hundred test rows, it worked fine.
The problem showed up in production after real data piled up.
A user clicked download for tens of thousands of rows, the screen froze for a long time, and the server crashed with OutOfMemoryError: Java heap space.</description>
    </item>
  </channel>
</rss>
