AWS Documentation » Neptune » User Guide » Best Practices: Getting the Most Out of Neptune

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
  • Best Practices for Using Neptune Metrics
  • Best Practices for Tuning Neptune Queries
  • Load Balancing Across Read Replicas
  • Loading Faster Using a Temporary Larger Instance
• Best Practices Using Gremlin
  • 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
  • Sharing a Single Gremlin Java Client Instance Across Multiple Threads
  • Create Separate Gremlin Java Client Instances for Read and Write Endpoints
  • Adding Multiple Read Replica Endpoints to a Gremlin Java Connection Pool
  • Explicitly Closing Gremlin Java Driver Connections to Avoid Connection Limit
  • Avoiding Memory Leaks Due to the Keep-Alive Bug in TinkerPop Gremlin Java Driver
  • Creating a New Connection After Failover
• 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