Best practices: getting the most out of Neptune

The following are some general recommendations for working with Amazon Neptune. Use this information as a reference to quickly find recommendations for using Amazon Neptune and maximizing performance.

Contents

• Amazon Neptune basic operational guidelines
  • Amazon Neptune security best practices
  • Enable the OSPG Index if you have a large number of predicates
  • Avoid long-running transactions where possible
  • Best practices for using Neptune metrics
  • Best practices for tuning Neptune queries
  • Load balancing across read replicas
  • Loading faster using a temporary larger instance
  • Resize your writer instance by failing over to a read-replica
  • Avoid different instance classes in a cluster
  • Retry upload after data prefetch task interrupted error
• General Best Practices for Using Gremlin with Neptune
  • Test Gremlin code in the context where you will deploy it
  • Structure upsert queries to take advantage of the DFE engine
  • Creating Efficient Multithreaded Gremlin Writes
  • Pruning Records with the Creation Time Property
  • Using the datetime( ) Method for Groovy Time Data
  • Using Native Date and Time for GLV Time Data
• Best practices using the Gremlin Java client with Neptune
  • Use the latest compatible version of the Apache TinkerPop Java client
  • Re-use the client object across multiple threads
  • Create separate Gremlin Java client objects for read and write endpoints
  • Add multiple read replica endpoints to a Gremlin Java connection pool
  • Close the client to avoid the connections limit
  • Create a new connection after failover
  • Set maxInProcessPerConnection and maxSimultaneousUsagePerConnection to the same value
  • Send queries to the server as bytecode rather than as strings
  • Always completely consume the ResultSet or Iterator returned by a query
  • Bulk add vertices and edges in batches
  • Disable DNS caching in the Java Virtual Machine
  • Optionally, set timeouts at a per-query level
  • Work around a keep-alive bug in clients earlier than 3.3.4
  • Troubleshoot Gremlin Java client exceptions
    • Troubleshoot java.util.concurrent.TimeoutException
• Neptune Best Practices Using SPARQL
  • Querying All Named Graphs by Default
  • Specifying a Named Graph for Load
  • Choosing Between FILTER, FILTER...IN, and VALUES in Your Queries
• Neptune Best Practices Using openCypher and Bolt
  • Neptune does not support multiple concurrent queries in a transaction
  • Create a new connection after failover
  • Connection handling for long-lived applications
  • Connection handling for AWS Lambda
  • Close driver objects when you're done
  • Use explicit transaction modes for reading and writing
    • Read-only transactions
    • Read-only transactions
  • Retry logic for exceptions