[jira] [Updated] (TINKERPOP-2934) Optimize ObjectWritable for displaying content of Java Collection or Map to reduce OOM
[ https://issues.apache.org/jira/browse/TINKERPOP-2934?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Valentyn Kahamlyk updated TINKERPOP-2934: - Fix Version/s: 3.7.0 3.6.3 3.5.6 > Optimize ObjectWritable for displaying content of Java Collection or Map to > reduce OOM > -- > > Key: TINKERPOP-2934 > URL: https://issues.apache.org/jira/browse/TINKERPOP-2934 > Project: TinkerPop > Issue Type: Improvement >Affects Versions: 3.6.2 >Reporter: Redriver >Priority: Major > Fix For: 3.7.0, 3.6.3, 3.5.6 > > Attachments: image-2023-04-27-15-08-10-874.png > > > OLAP query easily triggers OOM, I found a possible reason is > [https://github.com/apache/tinkerpop/blob/master/hadoop-gremlin/src/main/java/org/apache/tinkerpop/gremlin/hadoop/structure/io/ObjectWritable.java#L72] > dump a huge string output. See what I captureed from SparkUI. In fact, that > toString() does not make much sense for OLAP processing except for displaying > in UI. Furthermore, those too long string is not readable for people. So, > ideally the toString() for Map or Collection should be optimized to be java > class + size(). Then the OOM will disappear. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (TINKERPOP-2934) Optimize ObjectWritable for displaying content of Java Collection or Map to reduce OOM
[ https://issues.apache.org/jira/browse/TINKERPOP-2934?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Redriver updated TINKERPOP-2934: Attachment: image-2023-04-27-15-08-10-874.png > Optimize ObjectWritable for displaying content of Java Collection or Map to > reduce OOM > -- > > Key: TINKERPOP-2934 > URL: https://issues.apache.org/jira/browse/TINKERPOP-2934 > Project: TinkerPop > Issue Type: Improvement >Affects Versions: 3.6.2 >Reporter: Redriver >Priority: Major > Attachments: image-2023-04-27-15-08-10-874.png > > > OLAP query easily triggers OOM, I found a possible reason is > [https://github.com/apache/tinkerpop/blob/master/hadoop-gremlin/src/main/java/org/apache/tinkerpop/gremlin/hadoop/structure/io/ObjectWritable.java#L72] > dump a huge string output. See what I captureed from SparkUI. In fact, that > toString() does not make much sense for OLAP processing except for displaying > in UI. Furthermore, those too long string is not readable for people. So, > ideally the toString() for Map or Collection should be optimized to be java > class + size(). Then the OOM will disappear. -- This message was sent by Atlassian Jira (v8.20.10#820010)
