cayleygraph / cayleygraph/cayley

Performance, scaling and databases

Open
#716 6 comments 1 reaction 0 assignees View on GitHub
performance
Dominant language
Go
Stars
15.1k
Forks
1.2k
PR merge metrics
No merged PRs in 30d

Description

I'm aiming to process a lot of data as quickly as possible, and I'm finding the Postgres connection limit backing my Cayley is being the bottleneck. I started thinking: I can scale up, but maybe there is a bigger issue. It got me wondering about the general performance of Cayley, in particular how it scales with regards to different databases backing it. I looked around a bit and read (skimmed) [this](https://discourse.cayley.io/t/ultimate-direction-for-cayley/160/8).

I feel like it should be doable to set up performance testing with regards to different use-cases and backends. It can be done in fases, general perfomance testing first, backend specific testing later. My first thoughts would be to make use of CircleCI 2.0 here because of its affinity with docker. I'd be happy to help out, although I cannot pledge any time for now. In any case, I'm curious about your thoughts :smiley:.

Contributor guide

Open the contributing guide

Research direction

No files or tests are named. Start by defining the performance use cases and database backends to benchmark, then review the proposed CircleCI 2.0 and Docker approach; done should mean an agreed, repeatable benchmark plan and CI setup, but the issue does not specify concrete success criteria.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker, go, postgresql
Domain
ci-cd, databases, performance, testing-qa
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.