Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

OpenCTI and dependencies memory documentation #127

Closed
richard-julien opened this issue Jul 8, 2019 · 2 comments
Closed

OpenCTI and dependencies memory documentation #127

richard-julien opened this issue Jul 8, 2019 · 2 comments
Assignees
Labels
solved use to identify issue that has been solved (must be linked to the solving PR)
Milestone

Comments

@richard-julien
Copy link
Member

richard-julien commented Jul 8, 2019

Problem to Solve

Currently its not clear the amount of memory required to have openCTI running

Current Workaround

No

Proposed Solution

Write documentation about openCTI and dependencies.

  • Grakn (4go) + Inner cassandra (4go)
  • Elasticsearch (2go)
  • Redis (512 Mo)
  • RabbitMQ (256 Mo)
  • OpenCTI API. (64 Mo)
  • OpenCTI worker (64 Mo)
  • OpenCTI connector (64 Mo)

Hints

The Cassandra heap should be no less than 2GB, and no more than 50% of your system RAM
Heaps smaller than 12GB should consider ParNew/ConcurrentMarkSweep garbage collection
Heaps larger than 12GB should consider G1GC

@richard-julien richard-julien added this to the Release 1.1.0 milestone Jul 8, 2019
@SamuelHassine SamuelHassine self-assigned this Jul 8, 2019
@SamuelHassine
Copy link
Member

@richard-julien This will be in a specific documentation page with links to documentation of dependencies on how enforce memory limits (ElasticSearch, Grakn, Redis and Minio).

@richard-julien
Copy link
Member Author

I think we need to enforce a default configuration that work with the minimal requirement. And of course explains this choice in the doc.

@richard-julien richard-julien changed the title Memory enforce default configuration + recommandation OpenCTI and dependencies memory documentation Jul 17, 2019
@SamuelHassine SamuelHassine added the solved use to identify issue that has been solved (must be linked to the solving PR) label Jul 22, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
solved use to identify issue that has been solved (must be linked to the solving PR)
Projects
None yet
Development

No branches or pull requests

2 participants