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

SM OR - bad performance while encoding big data tables #159

DimaSol opened this Issue Aug 10, 2016 · 0 comments


None yet
2 participants

DimaSol commented Aug 10, 2016

When working with big data tables there is a duplicated call to setColumnIndex which is very expensive duo to the restore state of it. is there a way to prevent one of the calls?
Profiling traces with measurments and timings can be seen in the attached picture.

@YurinM YurinM assigned YurinM and unassigned YurinM Aug 11, 2016

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment