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

Implement performances test infrastructure #645

Closed
SamuelHassine opened this issue Apr 23, 2020 · 4 comments
Closed

Implement performances test infrastructure #645

SamuelHassine opened this issue Apr 23, 2020 · 4 comments
Assignees
Labels
feature use for describing a new feature to develop solved use to identify issue that has been solved (must be linked to the solving PR)
Milestone

Comments

@SamuelHassine
Copy link
Member

Problem to Solve

Be able to track ingestion performances in various use cases in time or from one version to the next one.

Current Workaround

Manual tests.

Proposed Solution

Deploy a performance test infrastructure with beautiful reports. Ask @SamuelHassine for various datasets (small, big, lot of embedded relations, lot of stix relations, lot of observables, etc.)

Additional Information

None.

@SamuelHassine SamuelHassine added build feature use for describing a new feature to develop labels Apr 23, 2020
@SamuelHassine SamuelHassine added this to the Release 3.1.2 milestone Apr 23, 2020
@cvdsouza
Copy link

this would be really useful especially for those adopting openCTI in prod, to gauge performance of deployment.

@richard-julien
Copy link
Member

Starting to work on it.

  • Global performance timing for specific amount of data to inject on different target architecture.
  • Specific metrics
    -- Memory allocation for opencti nodejs process.
    -- GraphQL response times
    -- Dependencies metrics??

@SamuelHassine
Copy link
Member Author

  • Memory allocation of Python processes
  • CPU consumption?
  • When the Python library is doing several calls (reading, then writing, then adding some embedded relations such as external references), it could be useful to have the timing of each of the calls.

@cvdsouza
Copy link

Just wondering here, I have seen errors like this constantly :

{"message":"[ELASTIC] 2afdd443-0405-4e89-a169-7c2d2bc85f80 missing, cant update the element, you need to reindex","level":"error"}
{"message":"[ELASTIC] d4c1410c-4ef4-48eb-8f1f-be1cdd66f505 missing, cant update the element, you need to reindex","level":"error"}

Questions / Recommendations :

  • Would there be a way to determine how long it would take to re-index ?
  • Metrics to determine if re-index is needed , i.e. elastic not in sync with grakn for some reason?

My thought around this was, it would help users understand if / when they should run a reindex.

@SamuelHassine SamuelHassine added the solved use to identify issue that has been solved (must be linked to the solving PR) label May 27, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature use for describing a new feature to develop 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

3 participants