neo4j 데이터베이스에 이상적인 aws 인스턴스 유형

Question

neo4j 3.2 버전이 설치되어 있습니다. Linux EC2 인스턴스. 이상적인 인스턴스 유형을 확인하고 있습니다.

neo4j 그래프에는 여러 프로젝트가 있으며 각 프로젝트는 약 50,000 개의 노드, 백만 개의 관계 및 약 100,000 개의 속성을 가질 수 있습니다. 단일 저장 조작은 최대 25k 노드, 75k 관계 W 10k 특성을 가질 수 있습니다. i2, d2, r 가장 큰 인스턴스 유형을 시도했습니다. 모든 "저장"작업에 필요한 모든 작업이 거의 1 분 이상 소요됩니다. 내 Windows 운영 체제에서 소요되는 최대 시간은 20 초입니다. 이 시나리오에서 이상적인 인스턴스 유형은 무엇입니까?

그리고 neo4j.conf 파일과 관련이 있는지 의심 스럽습니다. 리눅스 aws의 neo4j.conf에 언급 된 많은 jvm 매개 변수가 있습니다. 그들 중 누구도 내 Windows 시스템에 지정되어 있지 않습니다. 응용 프로그램이 자연 burstable 인 경우 16 (내가 t2.xlarge 같은 Burstable 성능 인스턴스를 추천 할 것입니다

1) :

#***************************************************************** 
# Neo4j configuration 
# 
# For more details and a complete list of settings, please see 
# https://neo4j.com/docs/operations-manual/current/reference/configuration-settings/ 
#***************************************************************** 

# The name of the database to mount 
#dbms.active_database=graph.db 

# Paths of directories in the installation. 
dbms.directories.data=/var/lib/neo4j/data 
dbms.directories.plugins=/var/lib/neo4j/plugins 
dbms.directories.certificates=/var/lib/neo4j/certificates 
dbms.directories.logs=/var/log/neo4j 
dbms.directories.lib=/usr/share/neo4j/lib 
dbms.directories.run=/var/run/neo4j 

# This setting constrains all `LOAD CSV` import files to be under the `import` directory. Remove or comment it out to 
# allow files to be loaded from anywhere in the filesystem; this introduces possible security problems. See the 
# `LOAD CSV` section of the manual for details. 
dbms.directories.import=/var/lib/neo4j/import 

# Whether requests to Neo4j are authenticated. 
# To disable authentication, uncomment this line 
#dbms.security.auth_enabled=false 

# Enable this to be able to upgrade a store from an older version. 
#dbms.allow_upgrade=true 

# Java Heap Size: by default the Java heap size is dynamically 
# calculated based on available system resources. 
# Uncomment these lines to set specific initial and maximum 
# heap size. 
# dbms.memory.heap.initial_size=512m 
#dbms.memory.heap.max_size=512m 

# The amount of memory to use for mapping the store files, in bytes (or 
# kilobytes with the 'k' suffix, megabytes with 'm' and gigabytes with 'g'). 
# If Neo4j is running on a dedicated server, then it is generally recommended 
# to leave about 2-4 gigabytes for the operating system, give the JVM enough 
# heap to hold all your transaction state and query context, and then leave the 
# rest for the page cache. 
# The default page cache memory assumes the machine is dedicated to running 
# Neo4j, and is heuristically set to 50% of RAM minus the max Java heap size. 
#dbms.memory.pagecache.size=10g 

#***************************************************************** 
# Network connector configuration 
#***************************************************************** 

# With default configuration Neo4j only accepts local connections. 
# To accept non-local connections, uncomment this line: 
dbms.connectors.default_listen_address=0.0.0.0 

# You can also choose a specific network interface, and configure a non-default 
# port for each connector, by setting their individual listen_address. 

# The address at which this server can be reached by its clients. This may be the server's IP address or DNS name, or 
# it may be the address of a reverse proxy which sits in front of the server. This setting may be overridden for 
# individual connectors below. 
#dbms.connectors.default_advertised_address=localhost 

# You can also choose a specific advertised hostname or IP address, and 
# configure an advertised port for each connector, by setting their 
# individual advertised_address. 

# Bolt connector 
dbms.connector.bolt.enabled=true 
#dbms.connector.bolt.tls_level=OPTIONAL 
#dbms.connector.bolt.listen_address=:7687 

# HTTP Connector. There must be exactly one HTTP connector. 
dbms.connector.http.enabled=true 
#dbms.connector.http.listen_address=:7474 

# HTTPS Connector. There can be zero or one HTTPS connectors. 
dbms.connector.https.enabled=true 
#dbms.connector.https.listen_address=:7473 

# Number of Neo4j worker threads. 
#dbms.threads.worker_count= 

#***************************************************************** 
# SSL system configuration 
#***************************************************************** 

# Names of the SSL policies to be used for the respective components. 

# The legacy policy is a special policy which is not defined in 
# the policy configuration section, but rather derives from 
# dbms.directories.certificates and associated files 
# (by default: neo4j.key and neo4j.cert). Its use will be deprecated. 

# The policies to be used for connectors. 
# 
# N.B: Note that a connector must be configured to support/require 
#  SSL/TLS for the policy to actually be utilized. 
# 
# see: dbms.connector.*.tls_level 

#bolt.ssl_policy=legacy 
#https.ssl_policy=legacy 

#***************************************************************** 
# SSL policy configuration 
#***************************************************************** 

# Each policy is configured under a separate namespace, e.g. 
# dbms.ssl.policy.<policyname>.* 
# 
# The example settings below are for a new policy named 'default'. 

# The base directory for cryptographic objects. Each policy will by 
# default look for its associated objects (keys, certificates, ...) 
# under the base directory. 
# 
# Every such setting can be overriden using a full path to 
# the respective object, but every policy will by default look 
# for cryptographic objects in its base location. 
# 
# Mandatory setting 

#dbms.ssl.policy.default.base_directory=certificates/default 

# Allows the generation of a fresh private key and a self-signed 
# certificate if none are found in the expected locations. It is 
# recommended to turn this off again after keys have been generated. 
# 
# Keys should in general be generated and distributed offline 
# by a trusted certificate authority (CA) and not by utilizing 
# this mode. 

#dbms.ssl.policy.default.allow_key_generation=false 

# Enabling this makes it so that this policy ignores the contents 
# of the trusted_dir and simply resorts to trusting everything. 
# 
# Use of this mode is discouraged. It would offer encryption but no security. 

#dbms.ssl.policy.default.trust_all=false 

# The private key for the default SSL policy. By default a file 
# named private.key is expected under the base directory of the policy. 
# It is mandatory that a key can be found or generated. 

#dbms.ssl.policy.default.private_key= 

# The private key for the default SSL policy. By default a file 
# named public.crt is expected under the base directory of the policy. 
# It is mandatory that a certificate can be found or generated. 

#dbms.ssl.policy.default.public_certificate= 

# The certificates of trusted parties. By default a directory named 
# 'trusted' is expected under the base directory of the policy. It is 
# mandatory to create the directory so that it exists, because it cannot 
# be auto-created (for security purposes). 
# 
# To enforce client authentication client_auth must be set to 'require'! 

#dbms.ssl.policy.default.trusted_dir= 

# Client authentication setting. Values: none, optional, require 
# The default is to require client authentication. 
# 
# Servers are always authenticated unless explicitly overridden 
# using the trust_all setting. In a mutual authentication setup this 
# should be kept at the default of require and trusted certificates 
# must be installed in the trusted_dir. 

#dbms.ssl.policy.default.client_auth=require 

# A comma-separated list of allowed TLS versions. 
# By default TLSv1, TLSv1.1 and TLSv1.2 are allowed. 

#dbms.ssl.policy.default.tls_versions= 

# A comma-separated list of allowed ciphers. 
# The default ciphers are the defaults of the JVM platform. 

#dbms.ssl.policy.default.ciphers= 

#***************************************************************** 
# Logging configuration 
#***************************************************************** 

# To enable HTTP logging, uncomment this line 
#dbms.logs.http.enabled=true 

# Number of HTTP logs to keep. 
#dbms.logs.http.rotation.keep_number=5 

# Size of each HTTP log that is kept. 
#dbms.logs.http.rotation.size=20m 

# To enable GC Logging, uncomment this line 
#dbms.logs.gc.enabled=true 

# GC Logging Options 
# see http://docs.oracle.com/cd/E19957-01/819-0084-10/pt_tuningjava.html#wp57013 for more information. 
#dbms.logs.gc.options=-XX:+PrintGCDetails -XX:+PrintGCDateStamps -XX:+PrintGCApplicationStoppedTime -XX:+PrintPromotionFailure -XX:+PrintTenuringDistribution 

# Number of GC logs to keep. 
#dbms.logs.gc.rotation.keep_number=5 

# Size of each GC log that is kept. 
#dbms.logs.gc.rotation.size=20m 

# Size threshold for rotation of the debug log. If set to zero then no rotation will occur. Accepts a binary suffix "k", 
# "m" or "g". 
#dbms.logs.debug.rotation.size=20m 

# Maximum number of history files for the internal log. 
#dbms.logs.debug.rotation.keep_number=7 

#***************************************************************** 
# Miscellaneous configuration 
#***************************************************************** 

# Enable this to specify a parser other than the default one. 
#cypher.default_language_version=3.0 

# Determines if Cypher will allow using file URLs when loading data using 
# `LOAD CSV`. Setting this value to `false` will cause Neo4j to fail `LOAD CSV` 
# clauses that load data from the file system. 
#dbms.security.allow_csv_import_from_file_urls=true 

# Retention policy for transaction logs needed to perform recovery and backups. 
dbms.tx_log.rotation.retention_policy=1 days 

# Enable a remote shell server which Neo4j Shell clients can log in to. 
#dbms.shell.enabled=true 
# The network interface IP the shell will listen on (use 0.0.0.0 for all interfaces). 
#dbms.shell.host=127.0.0.1 
# The port the shell will listen on, default is 1337. 
#dbms.shell.port=1337 

# Only allow read operations from this Neo4j instance. This mode still requires 
# write access to the directory for lock purposes. 
#dbms.read_only=false 

# Comma separated list of JAX-RS packages containing JAX-RS resources, one 
# package name for each mountpoint. The listed package names will be loaded 
# under the mountpoints specified. Uncomment this line to mount the 
# org.neo4j.examples.server.unmanaged.HelloWorldResource.java from 
# neo4j-server-examples under /examples/unmanaged, resulting in a final URL of 
# http://localhost:7474/examples/unmanaged/helloworld/{nodeId} 
#dbms.unmanaged_extension_classes=org.neo4j.examples.server.unmanaged=/examples/unmanaged 

#******************************************************************** 
# JVM Parameters 
#******************************************************************** 

# G1GC generally strikes a good balance between throughput and tail 
# latency, without too much tuning. 
dbms.jvm.additional=-XX:+UseG1GC 

# Have common exceptions keep producing stack traces, so they can be 
# debugged regardless of how often logs are rotated. 
#dbms.jvm.additional=-XX:-OmitStackTraceInFastThrow 

# Make sure that `initmemory` is not only allocated, but committed to 
# the process, before starting the database. This reduces memory 
# fragmentation, increasing the effectiveness of transparent huge 
# pages. It also reduces the possibility of seeing performance drop 
# due to heap-growing GC events, where a decrease in available page 
# cache leads to an increase in mean IO response time. 
# Try reducing the heap memory, if this flag degrades performance. 
dbms.jvm.additional=-XX:+AlwaysPreTouch 

# Trust that non-static final fields are really final. 
# This allows more optimizations and improves overall performance. 
# NOTE: Disable this if you use embedded mode, or have extensions or dependencies that may use reflection or 
# serialization to change the value of final fields! 
dbms.jvm.additional=-XX:+UnlockExperimentalVMOptions 
dbms.jvm.additional=-XX:+TrustFinalNonStaticFields 

# Disable explicit garbage collection, which is occasionally invoked by the JDK itself. 
dbms.jvm.additional=-XX:+DisableExplicitGC 

# Remote JMX monitoring, uncomment and adjust the following lines as needed. Absolute paths to jmx.access and 
# jmx.password files are required. 
# Also make sure to update the jmx.access and jmx.password files with appropriate permission roles and passwords, 
# the shipped configuration contains only a read only role called 'monitor' with password 'Neo4j'. 
# For more details, see: http://download.oracle.com/javase/8/docs/technotes/guides/management/agent.html 
# On Unix based systems the jmx.password file needs to be owned by the user that will run the server, 
# and have permissions set to 0600. 
# For details on setting these file permissions on Windows see: 
#  http://docs.oracle.com/javase/8/docs/technotes/guides/management/security-windows.html 
#dbms.jvm.additional=-Dcom.sun.management.jmxremote.port=3637 
#dbms.jvm.additional=-Dcom.sun.management.jmxremote.authenticate=true 
#dbms.jvm.additional=-Dcom.sun.management.jmxremote.ssl=false 
#dbms.jvm.additional=-Dcom.sun.management.jmxremote.password.file=/absolute/path/to/conf/jmx.password 
#dbms.jvm.additional=-Dcom.sun.management.jmxremote.access.file=/absolute/path/to/conf/jmx.access 

# Some systems cannot discover host name automatically, and need this line configured: 
#dbms.jvm.additional=-Djava.rmi.server.hostname=$THE_NEO4J_SERVER_HOSTNAME 

# Expand Diffie Hellman (DH) key size from default 1024 to 2048 for DH-RSA cipher suites used in server TLS handshakes. 
# This is to protect the server from any potential passive eavesdropping. 
dbms.jvm.additional=-Djdk.tls.ephemeralDHKeySize=2048 

#******************************************************************** 
# Wrapper Windows NT/2000/XP Service Properties 
#******************************************************************** 
# WARNING - Do not modify any of these properties when an application 
# using this configuration file has been installed as a service. 
# Please uninstall the service before modifying this section. The 
# service can then be reinstalled. 

# Name of the service 
dbms.windows_service_name=neo4j 

#******************************************************************** 
# Other Neo4j system properties 
#******************************************************************** 
dbms.jvm.additional=-Dunsupported.dbms.udc.source=rpm 

Answer 1

마침내 알아 냈습니다. neo4j 그래프 db의 경우 우분투 OS가 선호합니다. 인스턴스 유형에 대해서는 SSD 스토리지가있는 것이 바람직합니다. 그래서 우리는 M3.2xlarge로 갈 수 있습니다.

처리량을 증가시키는 IOPS를 구성해야합니다. 필요한 경우 힙 & 캐시 메모리를 설정하십시오.

Expand EBS Volume

Modify EBS volume

Answer 2

지정한 구성과주고에 따르면 recommended system requirements in documentation at the official neo4j site 나는이 인스턴스를 제안 GB RAM, 인텔 제온 패밀리 프로세서, 적당한 네트워킹 성능) 또는 t2.2xlarge (32 GB RAM, Intel Xeon 패밀리 프로세서, 적당한 네트워킹 성능). 응용 프로그램이 범용이며 높은 구성을 요구하는 경우

2) 내가 추천 :

을 비용이 큰 관심사 m3.xlarge (4 vCPU 한 경우, 15기가바이트 RAM, 인텔 제온 E5-2670 v2를, 높은 네트워킹 성능, 2 × 40 SSD), m3.2xlarge (8의 vCPU, 30기가바이트 RAM, 인텔 제온 E5-2670 v2의 높은 네트워킹 성능, 2 × 80 SSD는)

또는

당신이 만약 최신 및 일반 세대 인스턴스를 원합니다. m4.xlarge (4 개의 vCPU, 16GB RAM, Intel Xeon E5-2676 v3, 높은 네트워킹 성능, EBS 전용 저장소), m4.2xlarge (8 개의 vCPU, 32GB RAM, Intel Xeon E5-2676 v3, High 네트워킹 성능, EBS 전용 저장소).

인스턴스 유형에 대한 자세한 내용은 here을 참조하십시오.