<html> <head> <base href="https://bugs.documentfoundation.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - Allow more than 1024 columns in calc" href="https://bugs.documentfoundation.org/show_bug.cgi?id=50916#c72">Comment # 72</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - Allow more than 1024 columns in calc" href="https://bugs.documentfoundation.org/show_bug.cgi?id=50916">bug 50916</a> from <a class="email" href="mailto:emilymabrey93@gmail.com" title="Emily Mabrey <emilymabrey93@gmail.com>"> Emily Mabrey</a> <pre>Is making a truly dynamic sheet even needed? Excel only allows a static number of columns and a static number of rows and it seems like a massive undertaking for such a seemingly niche application. Excel 2016/ M365 supports 1,048,576 rows or 16,384 columns as that static limit. Looking over the comments I can see that there may have already been an effort to produce a dynamically sized sheet. Has anyone done testing to see if the dynamic sheet comes with any performance penalty? If so it might be wise to use a large static value under most cases and allow the dynamic sizing as a niche option with an opt-in configuration. That would prevent constant allocation/frees around when adding and removing rows and cols if that does turn out to be a performance problem. I would look into the performance consequences myself, but I am brand-new to this project and wholly unfamiliar with the code base and procedures for performance monitoring of this project. If anyone could point me to some guiding documentations I would be willing to make an effort at fulfilling my own request.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>