WeSearch

Splitting Correctness from Throughput: A Hybrid Approach to XLSX Streaming Writes

·5 min read · 0 reactions · 0 comments · 4 views
#java#programming#performance#architecture#xlsx#Apache POI#XSSFWorkbook#SXSSFWorkbook#FastExcel#ECMA-376
Splitting Correctness from Throughput: A Hybrid Approach to XLSX Streaming Writes
⚡ TL;DR · AI summary

The article presents a hybrid approach to writing XLSX files that separates concerns of OOXML correctness and per-cell throughput by combining Apache POI for structural correctness and StringBuilder for high-performance cell writing. It proposes generating a correct XLSX skeleton with POI and streaming cell data directly via text manipulation, reducing object allocation and write time. Benchmarks show significant performance improvements over existing methods while maintaining compatibility with Excel's format requirements.

Original article
DEV.to (Top)
Read full at DEV.to (Top) →
Opening excerpt (first ~120 words) tap to expand

try { if(localStorage) { let currentUser = localStorage.getItem('current_user'); if (currentUser) { currentUser = JSON.parse(currentUser); if (currentUser.id === 991167) { document.getElementById('article-show-container').classList.add('current-user-is-article-author'); } } } } catch (e) { console.error(e); } scndry Posted on Apr 30 Splitting Correctness from Throughput: A Hybrid Approach to XLSX Streaming Writes #java #programming #performance #architecture Writing XLSX files involves two concerns that have nothing to do with each other: OOXML correctness — relationships, content types, namespace declarations, theme references, drawing rels. Get these wrong and Excel may refuse to open the file or report a recovery dialog. The complexity is bounded but the surface is large.

Excerpt limited to ~120 words for fair-use compliance. The full article is at DEV.to (Top).

Anonymous · no account needed
Share 𝕏 Facebook Reddit LinkedIn Threads WhatsApp Bluesky Mastodon Email

Discussion

0 comments

More from DEV.to (Top)