Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Should I avoid to use sstCacheSize feature ? #233

Open
danmaidesenling opened this issue Mar 31, 2021 · 0 comments
Open

Should I avoid to use sstCacheSize feature ? #233

danmaidesenling opened this issue Mar 31, 2021 · 0 comments

Comments

@danmaidesenling
Copy link

danmaidesenling commented Mar 31, 2021

Hi All,
Firstly, thanks for your contribution to this bravo project. And I see a tips below about sstCacheSize.
So, Should I avoid to use sstCacheSize feature ?
/**
*

!!! This option is experimental !!!


*
* Set the size of the Shared Strings Table cache. This option exists to accommodate
* extremely large workbooks with millions of unique strings. Normally the SST is entirely
* loaded into memory, but with large workbooks with high cardinality (i.e., very few
* duplicate values) the SST may not fit entirely into memory.
*


* By default, the entire SST will be loaded into memory. Setting a value greater than
* 0 for this option will only cache up to this many entries in memory. However,
* enabling this option at all will have some noticeable performance degredation as you are
* trading memory for disk space.
*
* @param sstCacheSize size of SST cache
* @return reference to current {@code Builder}
*/
public Builder sstCacheSize(int sstCacheSize) {
this.sstCacheSize = sstCacheSize;
return this;
}

@danmaidesenling danmaidesenling changed the title !!! This option is experimental !!! Should I avoid to use sstCacheSize feature ? Apr 1, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant