Uh oh!
There was an error while loading. Please reload this page.
Feat kryo max buffersize - #735
Conversation
AmplabJenkins
commented
May 11, 2014
Can one of the admins verify this patch? |
mateiz
commented
May 12, 2014
Hey, so is this a new feature that was recently added to Kryo? Seems super useful, but in this case, I'd actually make the max buffer size higher by default. Or we can use the old setting as a max, and create a new setting for the initial buffer size. |
mateiz
commented
May 12, 2014
Jenkins, this is ok to test |
AmplabJenkins
commented
May 12, 2014
Merged build triggered. |
AmplabJenkins
commented
May 12, 2014
Merged build started. |
AmplabJenkins
commented
May 12, 2014
Merged build finished. All automated tests passed. |
AmplabJenkins
commented
May 12, 2014
All automated tests passed. |
koertkuipers
commented
May 12, 2014
hey matei, created jira here: only reason to be careful with this feature is that there is some overhead on buffer resizing (each time a new array is created with twice the size and the data is copied), which is why i was reluctant to make the old setting as a max. how about defaults 2MB for initial and 16MB for max? |
AmplabJenkins
commented
May 14, 2014
Merged build triggered. |
AmplabJenkins
commented
May 14, 2014
Merged build started. |
AmplabJenkins
commented
May 14, 2014
Merged build finished. All automated tests passed. |
AmplabJenkins
commented
May 14, 2014
All automated tests passed. |
pwendell
commented
May 28, 2014
This looks good to me! @koertkuipers mind updating the docs to include this (maybe wait until after #880 is merged tomorrow)? Also, mind prefixing the title here with SPARK-1811, this allows our merge script to detect the JIRA and link it. |
mateiz
commented
May 29, 2014
Hey one other thought, is there a reason to have the max this low? It might be good to make it even higher to deal with the odd large object (e.g. people working with large text documents). I'd go for 64 MB. |
pwendell
commented
Jun 4, 2014
@koertkuipers any interest in updating the docs and bumping the default? This would be a good change to have. |
koertkuipers
commented
Jun 20, 2014
hey sorry somehow misses this conversation thread. sure will update On Wed, Jun 4, 2014 at 1:48 AM, Patrick Wendell notifications@github.com
|
AmplabJenkins
commented
Jun 21, 2014
Merged build triggered. |
AmplabJenkins
commented
Jun 21, 2014
Merged build started. |
AmplabJenkins
commented
Jun 21, 2014
Merged build finished. |
AmplabJenkins
commented
Jun 21, 2014
Refer to this link for build results: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/15984/ |
koertkuipers
commented
Jun 23, 2014
not sure if i am supposed to deal with these failures? On Sat, Jun 21, 2014 at 1:52 PM, UCB AMPLab notifications@github.com
|
pwendell
commented
Jul 7, 2014
Jenkins, retest this please. |
AmplabJenkins
commented
Jul 7, 2014
Merged build triggered. |
AmplabJenkins
commented
Jul 7, 2014
Merged build started. |
AmplabJenkins
commented
Jul 7, 2014
Merged build finished. All automated tests passed. |
AmplabJenkins
commented
Jul 7, 2014
All automated tests passed. |
mingyukim
commented
Jul 9, 2014
Hi all, is there any update on this PR? |
koertkuipers
commented
Jul 9, 2014
i updated docs and defaults as requested. currently waiting for feedback or On Wed, Jul 9, 2014 at 6:46 PM, mingyukim notifications@github.com wrote:
|
pwendell
commented
Jul 17, 2014
Jenkins, retest this please. @koertkuipers mind creating a JIRA for this (we're trying to track all changes now). I can merge this in once we have an issue for it. |
SparkQA
commented
Jul 17, 2014
QA tests have started for PR 735. This patch merges cleanly. |
koertkuipers
commented
Jul 17, 2014
https://issues.apache.org/jira/browse/SPARK-2543 On Wed, Jul 16, 2014 at 9:53 PM, Apache Spark QA notifications@github.com
|
SparkQA
commented
Jul 17, 2014
QA results for PR 735: |
mateiz
commented
Jul 30, 2014
Author: Koert Kuipers <koert@tresata.com> Closesapache#735 from koertkuipers/feat-kryo-max-buffersize and squashes the following commits: 15f6d81 [Koert Kuipers] change default for spark.kryoserializer.buffer.max.mb to 64mb and add some documentation 1bcc22c [Koert Kuipers] Merge branch 'master' into feat-kryo-max-buffersize 0c9f8eb [Koert Kuipers] make default for kryo max buffer size 16MB 143ec4d [Koert Kuipers] test resizable buffer in kryo Output 0732445 [Koert Kuipers] support setting maxCapacity to something different than capacity in kryo Output
* KE-11534 Upgrade Janino to 3.1.6 for Calcite 1.30 * KE-11534 [Follow up]Fix for null vs true/false comparisons in TDVT SQL626 brought by Calcite 1.30
No description provided.