[
https://issues.apache.org/jira/browse/TINKERPOP-1063?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stephen mallette updated TINKERPOP-1063:
----------------------------------------
Fix Version/s: (was: 3.1.1-incubating)
3.2.0-incubating
Uncovered a reason to not try to merge this for 3.1.1 - failing tests. Not
sure what should be done exactly, but calls to {{vertices()}} and {{edges()}}
now lazily validate their arguments. To change that will break the current
contracts enforced by TP3 tests. Need to either:
1. change the contract expectations (which would be a breaking change for all)
2. change TinkerGraph to validate all arguments upfront.
I suspect we'd do the latter - but not in the hours before code freeze.
> TinkerGraph performance enhancements
> ------------------------------------
>
> Key: TINKERPOP-1063
> URL: https://issues.apache.org/jira/browse/TINKERPOP-1063
> Project: TinkerPop
> Issue Type: Improvement
> Components: tinkergraph
> Affects Versions: 3.1.0-incubating
> Reporter: stephen mallette
> Assignee: stephen mallette
> Fix For: 3.2.0-incubating
>
>
> Improve TinkerGraph performance in relation to the Ferma Benchmark which
> shows a reasonably wide gap between TP2 and TP3. We probably won't achieve
> parity with Blueprints but it would be nice to carve away some time to lessen
> the gap.
> https://github.com/Syncleus/Ferma-benchmark
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
